49 ms·
I don't really see the difference between most modern JavaScript "frameworks". It's mostly in the details, and any of them would work just fine. At this point i
by mrweasel 10y ago
I don't really see the difference between most modern JavaScript "frameworks". It's mostly in the details, and any of them would work just fine. At this point it's like arguing which of X number of programming languages are the best.
Part of seems to be: "How dare people not like the tool I prefer", or simply that people don't want to be bothered to learn yet another JavaScript library (which I can understand, but I'm not being prevented from using the tools I like, just because React exists).
One "mistake" I see React make, others do too, is mixing JavaScript and HTML. I'm still firmly in the camp that believes in progressive enhancement as the correct way of developing for the web. React, Angular and most other modern libraries doesn't seem to share that view.
- mack73 10y agoFirst time I read a blog post about react and saw it's artifacts so to speak I threw up in my mouth. Js AND HTML, mixed! Wtf? I spoke about this to lots of front-enders who laughed and called me old. I agree with your point. If markup and UI code can be separated, why wouldn't you strive for such a solution?
- meira 10y agoBecause HTML is not a programming language thus you have very limited options to work with.
- atom-morgan 10y agoThis is the best comment in the thread. And as if tech hiring wasn't bad enough already nearly every company hires with the expectation that you have hands-on professional experience with the framework as if it would take years to jump from Angular to React. If you're comfortable with at least one JavaScript framework, I don't see it taking anyone very long to acquire the knowledge to start working on another.