5 ms·
To me the question is more "do you really need a SPA" rather than "do you really need a framework for your SPA". Way to many websites are using unecessary SPA
by cm2187 10y ago
To me the question is more "do you really need a SPA" rather than "do you really need a framework for your SPA".
Way to many websites are using unecessary SPA which create more oportunities for things breaking, being incompatible, or taking longer to load than plain old server side html (plus with a flicker effect).
If you are really running an html application like an online trading platform then yes. But if you are a banking website and just want to display an account balance or the last 30 transactions, I fail to see why using a SPA makes sense. And I am not even talking about podcast websites or blogs where using an SPA is just absurd.
But as I noticed where I work, developpers are too often choosing technologies not based on the problem they are trying to solve, but based on the sort of keyword they want to see on their CVs. So I end up having to use hadoop for accessing 10MB csv files and dealing with similar moronic design decisions.
- PaulRobinson 10y agoThere are points in this article that go beyond SPA. In fact, I'd drop "for your SPA" from the title, and just use SPAs as an example. The author didn't, because, you know, he has a book to sell on SPAs, but let's let that slide. ;) All the arguments he makes can be made about any framework, including server-side. Every point of pain he cites I can relate to from use of frameworks like Rails, Symfony, hell the abuse of Wordpress might qualify here. Rails in particular: I was coding in Rails pre-1.0. Every major version upgrade has been hellish at some level. Often developers don't quite know what's going on only to find that callbacks or validations aren't working as expected. We can still write awesome Ruby applications using all the libraries that make up Rails, but would I start with Rails these days? I'm not sure I would unless I was going to be working with a team that was quite junior where the gains from conventional layouts and inner workings might give us some gains. That said, I'd also be transparent with them and myself about the costs of choosing a framework, any framework, and Rails is cheap in the short-term but I've seen it get expensive in the long term. Not because it's Rails or Ruby, but because it's a framework. I used to think the lack of a decent CQRS framework in most languages was a problem. I now think it might be an advantage. As that pattern becomes more popular for complex domains, it's forcing developers to write better software, and I think somehow most of them are realising this is the way to go. Perhaps that's just my bias. And it's also why Go is refreshing to me, personally. Frameworks are resisted by the community, primarily for performance reasons, but I actually think the author's arguments apply there too: with good enough library support we can get reuse whilst also not suffering IoC issues.
- tboyd47 10y agoBingo. SPA is what I like to call "non-existent technology," meaning a buzzword that is neither a real technology people can download and use, nor a specification people can refer to. Other examples: "Cloud computing," "NoSQL," "SOA." It only really exists on people's resumes and on blog posts. Non-technical people have no way of knowing that it is not real. There are good reasons why web applications have backends. There are also good reasons why you would use that backend to serve pre-rendered HTML. There are also good reasons why you would use page transitions to take the user from one screen to another. These concepts are lost on many developers nowadays. I'm not saying you never want an SPA, but it's really freaking hard to do because you're going against the grain on a platform with 20 years of progress in another direction. What happens when non-existent technology makes up the greater part of the beginner's stack? When instead of the LAMP stack or Ruby on Rails, people graduate coding bootcamps with a specialty in building functional SPAs using NoSQL and cloud-based BFFs?
- paulddraper 10y agoFor cloud computing not being real, there is a lot of money being spent/made on it. "Cloud computing," "NoSQL," "SOA" are concepts/ideas. They aren't "technologies" per say. There are, however, technologies that implement these ideas (AWS, CouchDB, Ostrich).
- deleted 10y ago[deleted]
- tboyd47 10y agoI am only making a point that concepts/ideas are not the same as technologies, and shouldn't be treated as if they are. It's gotten so out of hand now that I half-expect people to start attaching version numbers to them, like "NoSQL 2.0". It's as if the phenomenon of a "technology buzzword" has been totally divorced from the technical product the buzzword is supposed to refer to, which is frustrating. If I have a resume full of concepts/ideas and no actual technologies, then the fact is that I can't be trusted to extend or repair any real system. The beauty of open source is that I do have skills I can take from company to company. I can use my Rails experience at one company to hit the ground running at another. If we start replacing actual technologies with mere concepts in our trade, then we still have a shared language but no shared skills. So the end result is eventually the same as if open source never happened and every programming environment was proprietary. End rant.