3 ms·
You're right that it's not javascript's fault per se. But the rest of your comment represents a narrow, dated and frankly ignorant viewpoint. Component-based fr
by chrisweekly 7y ago
You're right that it's not javascript's fault per se. But the rest of your comment represents a narrow, dated and frankly ignorant viewpoint. Component-based front-end architecture has tremendous advantages. And if you want to see "one big mess", simply examine the CSS of virtually any moderately-sized website or web application.
I've been doing web-related development since the late 90's, and I make a living as a UI Architect. Increasingly my clients are looking for my help to unfk their nightmarish, effectively unmaintainable legacy codebases -- which typically have followed this same cargo-cult "wisdom" to their detriment.
- krapp 7y agoI'll just vaguely gesture in the general direction of the multitudes of developers on HN who both work with front-end frameworks and complain ceaselessly about what a nightmare it is and stand by my statement. It can have both tremendous advantages and be a mess. Both can be, and are, true.
- airstrike 7y agoo/
- chrisweekly 7y agoFair point.
- mhd 7y agoComponent-based architecture doesn't imply JS-based versions of HTML and/or CSS, though. React does it that way, e.g. web components don't. Not that I'm averse to "reinventing" HTML or CSS in the first place, although doing that in JS would be somewhat ironic.
- chrisweekly 7y agoHuh? How do you think web components are implemented? Hint: they're JS APIs.
- mhd 7y agoWhen we're talking about reinventing HTML, there's a bit of a difference between a regular block of HTML between template tags and JSX I'd say.