2 ms·
> SPAs have been kicking around for, what, a decade? Only with big players: facebook, gmail, etc. Small crew SPA usually suck big time precisely because ther
by sametmax 8y ago
> SPAs have been kicking around for, what, a decade?
Only with big players: facebook, gmail, etc.
Small crew SPA usually suck big time precisely because there is not django/ror/etc equivalent for SPA. So people write it by hand. And they don't all have the talent pool and money the GAFAs have.
- eropple 8y agoSmall crew web apps usually suck, too. I have yet to see React (not to exclude Vue etc., React is what I use) make a nontrivial one worse than it otherwise would be, if only because it forces some semblance of separation of concerns upon the developer. (And, speaking personally, my now-standard stack of TypeScript/Express/TypeORM/tsoa provides a level of architectural enforcement I've only really gotten previously on the JVM, but with significantly less mucking around with my runtime.)
- sametmax 8y agoIt would be pretty hard to mess up a hackernews clone. A HN clone SPA though... First, let's see if they can get code splitting right to not make it loads 3mo/page. Then if they can choose a stack that doesn't kill navigation. Also, let's see how long it takes both team to come up with the same result. My money is on the static stack. Just the registration without a good framework is plenty of fun. Not that you can't make a SPA with an old school framework. But for some reason, SPA lovers will often go full nodejs as well, which is basically 1000 of libs you have to hand picks and fuse together. I work on more and more SPA every day. It's always the same deal: the cost is higher, and it needs smarter devs. Bottom line: do one when it has a good added value for your users.