3 ms·
I honestly hate SPA's. They're not necessary in almost every single use-case, yet everybody is shifting their shit into one.
by rabuse 6y ago
I honestly hate SPA's. They're not necessary in almost every single use-case, yet everybody is shifting their shit into one.
- renlo 6y agoIt’s because frontend devs are taught to use react, so suddenly every website unnecessarily becomes a react app. If every tutorial and class out there teaches people to use hammers (react) then people start using hammers to screw in a lightbulb or perform surgery.
- slowmovintarget 6y agoWhy SPAs? They're good when you develop capabilities API-first. When we build features, we follow an approach of making the feature possible (customer support can exercise the feature with PostMan or cURL) then making it friendly with a UI. There will be some tweaks and changes to the API to support the UI, but it's rarely drastic, and it ensures that every single capability we build out can be exercised by some other kind of program somewhere. If you're building components of a larger system (which we do), SPAs and web components atop back-end APIs make sense. If you're building a one-off fill-out form kind of application... No those don't make sense. You don't even need JavaScript for those, if you degrade into just HTML + CSS for users that have shut off JS.
- axguscbklp 6y agoEven if you develop capabilities API-first, you don't need an SPA, though. You can create some backend code that consumes your API and in turn serves separate web pages to a front end.
- tyingq 6y agoI really believe it's a case of resume driven development. I'm sure there are counter-examples, but the whole move to SPAs, from my vantage point, has been driven by tech people and not leaders. Self-inflicted.
- emteycz 6y agoYou're making software engineers way more important than they are. They don't hold this kind of decision power except in the smallest companies. In most cases of SME and large enterprises, there is a VP, a director or sometimes a "chapter lead" pushing it (in my experience, 9/10 times they believe this push will get them a promotion, as they "helped to move the company towards an important new technology"); has nothing to do with resumes.
- tyingq 6y agoI've had the opposite experience in this specific case.
- danjac 6y agoWhile RDD is a thing, the root cause is the stakeholders' requirements for more sophisticated and complex sites (whether smoother page transitions, more intricate effects, incessant demands to spy on every user interaction etc). It became harder and harder to do all this with server rendering and a rat's nest of jQuery. JS frameworks arose to meet these requirements and became an industry standard, and developers responded to market demand. It's all gone too far of course, but the stakeholders were as much to blame as anyone.
- tyingq 6y agoYes, I agree for those cases where the SPA was created to match customer expectations. I'm talking about using it where it doesn't belong, which happens quite a lot.