Re:Why I’m thankful for JavaScript fatigue
by tpolischuk on Tuesday November 29, 2016 @02:40PM
(#13065647)
That's actually kind of interesting. HTML/CSS/JS really are the framework. It's already a great separation of concerns (HTML for data/content, Javascript for behavior and logic, and CSS for presentation). Everything on top of it just seems like implementation details.
Re:Why I’m thankful for JavaScript fatigue
by elmigranto on Tuesday November 29, 2016 @02:58PM
(#13065777)
If you want to display documents, sure, I agree. If you need complex UIs, manually updating DOM without any kind of abstraction is definitely not a right choice.
Re:Why I’m thankful for JavaScript fatigue
by ktRolster on Wednesday November 30, 2016 @12:12AM
(#13068645)
No, CSS/HTML in theory is a good idea, separating content from presentation. In practice, the HTML still needs to know about the presentation.
Re:Why I’m thankful for JavaScript fatigue
by abritinthebay on Tuesday November 29, 2016 @03:01PM
(#13065790)
I find that it's the people that don't know HTML/CSS that have the problems.
They end up reinventing the wheel repeatedly.
There's a whole lot of JavaScript devs out there that think they are front-end devs. They aren't. There's nothing wrong with that of course.
Re:Why I’m thankful for JavaScript fatigue
by webmaven on Tuesday November 29, 2016 @04:22PM
(#13066385)
> They end up reinventing the wheel repeatedly.
You mean like altering attributes directly on elements (and proud that they had encapsulated the code in a reusable function) instead of adding/removing a class?
That's because front-end development is based on a core of HTML/CSS/JS which itself does not lend very well to architectural paradigms.
People 'starting out' on the front-end, in some ways, never learn how to write propers software. They've been using weird ideas from the start.