undefined | Better HN

Skip to content

Top Best Ask Show New Jobs

0 pointstomc19854y ago0 comments

Funny you say that, I have the same feelings about putting arbitrary HTML in my JS with React. Seems like we've all collectively forgotten about separation of concerns?

Give me templated HTML any day of the week please :)

0 comments

4 comments · 2 top-level

friedman234y ago· 2 in thread

> separation of concerns

I learned it and started developing this way taking separation of concerns as dogma and now I look back and wonder why we ever did it that way.

sodapopcan4y ago

The thing is that this was never "separation of concerns", it was always "separation of languages". There were cross cutting concerns across each language (CSS doing layout, styling, animations; JS doing business logic, animations, layout, styling; etc).

Mixing your JS/Other Language/CSS/HTML into components is a separation of concerns that really matters: separation of business/application concerns. Having everything you need that works together to solve a problem in place is very powerful (not to mention convenient).

tomc1985OP4y ago

The separation of languages is a natural byproduct of each language being specific to its domain. HTML does layout. CSS does styling. JS does frontend functionality. Server enforces business logic, controllers, and the data model.

It's clean, clear-cut, easy for IDE's to parse, and everything is in its place.

Dogma or not I still prefer everything in its place vs trying to watch my IDE twist itself in knots trying to figure out which language to use for a given context. To say nothing of all the little eccentricities in the JS engines' reimplemented parsers.

ch4s34y ago

With thins like LiveView, you're encouraged to have separate Heex files most of the time, and to keep them free of logic, other than the odd if statement.

j / k navigate · click thread line to collapse