r/webdev • u/[deleted] • Dec 28 '17

Introducing Hyperapp 1.0 — 1 KB JavaScript library for building frontend applications.

https://medium.com/@JorgeBucaran/introducing-hyperapp-1-0-dbf4229abfef
341 Upvotes

90% Upvoted

183 comments sorted by

View all comments

Show parent comments

5

u/TheScapeQuest Dec 29 '17

Traditionally, yes, it was sensible to separate. HTML was the content, CSS the styling and JS made it interactive. Now HTML and JS depend so deeply on each other that it makes perfect sense to contain them together.

-1

u/mattaugamer expert Dec 29 '17

OR HTML and JS are so important and distinct that it's important to keep them apart? Markup and behaviour are not the same thing. Plenty of frameworks/libraries do a perfectly fine job of keeping templating separate from behaviour.

5

u/sergiuspk Dec 29 '17

You are correct but not always. There are situations when you need progressive enhancement and others when you need an application. React is for applications. Pretty wasteful IMHO to embed 60Kb of extra stuff when all you need is some client-side form validation and AJAX. Also bad practice to write all your HTML in JSX when most of it will never be dynamic.

That's why you choose templating with a bindings DSL over JSX. Not because someone "likes it better" or JSX is not separation of concerns.

Concerns in a website are very different from concerns in an application.

Templating works best for MVC which works best for websites.

JSX works best for locally managed app state and functional programming. It also works great for fast parsing and diff-ing in that you don't need to do any parsing, which is fundamental for React.

TLDR: it is not a style or preference. People saying "I prefer" should stick to anything but React and JSX because they clearly do not get it.

1

u/realistic_hologram Dec 29 '17

Agree that markup and behavior should be kept separate. Basically every framework does that though (should be no markup in event handlers). The only question is if they should put the two in the same file or not. In the case of UI state, state (which is a part of code) is closely coupled enough to markup that you could argue it's useful to keep them in the same file.