4 ms·
This article seems to start with the premise that JS-heavy frontends improve the developer experience. This, I would heavily challenge. Compared to a Rails, Dj
by mifreewil 8y ago
This article seems to start with the premise that JS-heavy frontends improve the developer experience. This, I would heavily challenge.
Compared to a Rails, Django, Express.js, or any similar more-traditional framework that does server-side rendering with HTML templates, a little bit of JS and AJAX sprinkled in, SPA apps with frameworks like React are significantly more complex and requires more specialized knowledge on the frontend. I'm just starting to dive into React and Redux, and the amount of jargon and complexity is mind-blowing. All to solve the complexities of what? Bigco's massive bloated app with thousands of developers working on it?
- wgerard 8y ago> Compared to a Rails, Django, Express.js, or any similar more-traditional framework... SPA apps with frameworks like React are significantly more complex Hmm, I don't agree with that at all. I work with Rails and React daily, and they're about equal complexity to me - React just tries to hide it less. Rails especially can get incredibly complex the second you try to do something in a way that's not the "approved way".
- dagoat 8y agoDo you have any examples of incredibly complex rails? Also, I thought rails was supposed to be a lot of magic - hiding the complexity from the developer
- wgerard 8y agoHey! Sorry, I missed this comment. It's changed recently I've heard, but up until recently making a model without using ActiveRecord was a huge PITA that mostly engendered "don't do that" comments.
- acemarke 8y agoHi, I'm a Redux maintainer, and spend a lot of time answering questions about React too. Any specific concerns I can help with?