Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

It's time for modern CSS to kill the SPA

jonoalderson.com

Post reply on HN
Print view View original

211–220 of 516 posts

Re: It's time for modern CSS to kill the SPA

#211

Post by Tokumei-no-hito »

frollogaston wrote: post #183
ivape wrote: post #54

Earlier quoted context omitted.

There was a war? News to me. Saying Next won is like saying React won. Nothing won, everyone just latched on to what they thought the crowd vetted. The blind can't lead each other. Most people that stuck to Angular or minimal or no-frameworks are truly wondering what the fuck are all these people talking about? . Even the Facebook docs point straight to Next Startups and SV jerk each other off by promoting each other…

Kinda is a war unless you're working solo, cause you're gonna get forced to use something or another. When I tried a few solo web projects instead of just being a backend guy, I picked up React on my own because it was the only thing that makes sense. The page does what the code says. And that was after trying other things. Now I gotta occasionally use Angular, and it's boilerplate hell. Adding one button involves ed…

in the world of frameworks it's obvious that

html in your JS > JS in your html.

angular is a mess. it's the java of web frameworks. if you want up be enterprise(tm) go for it. I’m convinced it's only a thing because it gives people job security since nobody else chooses to touch it.

Re: It's time for modern CSS to kill the SPA

#214

Post by gjtorikian »

kassner wrote: post #75
buffalobuffalo wrote: post #26

Earlier quoted context omitted.

I don't know if a bunch of sloppy jQuery modules were ever really a viable option for an SPA. People tried to do it, sure, but I'd say the SPA era really started with backbone.js

ExtJS/Sencha was quite powerful and complete. I’ve built tons of SPAs with it in the late 00s.

Wow, I remember Sencha! It’s been a while since I’d heard that name.

Re: It's time for modern CSS to kill the SPA

#215

Post by 65 »

The SPA test should be: can you keep a picture-in-picture video element playing while navigating between pages?

If the vanilla web can't do this easily, then it's not a good solution to your need for a SPA.

Re: It's time for modern CSS to kill the SPA

#216

Post by bobthepanda »

paradox460 wrote: post #207
wolpoli wrote: post #192

Earlier quoted context omitted.

Honest question: Where are the places with low-bandwidth internet? Are we talking about cruise ships and satellites internet use cases?

Anyone attending a major event, or in a disaster zone. Things are getting better, but if you live near a ball park or something, there will be periodic times when your cellular Internet is unusable

Also, anyone traveling on a train or motor vehicle will just sometimes have worse reception, particularly with anything like a tunnel.

Re: It's time for modern CSS to kill the SPA

#217

Post by bobthepanda »

QuadrupleA wrote: post #76
codingdave wrote: post #14

SPAs make sense when your users have long sessions in your app. When it is worth the pain to load a large bundle in exchange for having really small network requests after the load. Smooth transitions are a nice side effect, but not the reason for an SPA. The core argument of the article, that client-side routing is a solution for page transitions, is a complete misunderstanding of what problems SPAs solve. So absolu…

Side note, sick of jQuery being always associated with spaghetti in the tech lexicon. Any Turing-complete system is spaghetti in the hands of bad programmers. And simple & clear in the hands of good ones who know how to design.

Jquery is good for dom manipulation, though most of the best ideas have become vanilla javascript standards.

It isn’t really equipped or opinionated on statefulness, which means that everybody was at one point kludging stuff onto it that didn’t make sense.

Re: It's time for modern CSS to kill the SPA

#219

Post by thro1 »

codingdave wrote: post #14

SPAs make sense when your users have long sessions in your app. When it is worth the pain to load a large bundle in exchange for having really small network requests after the load. Smooth transitions are a nice side effect, but not the reason for an SPA. The core argument of the article, that client-side routing is a solution for page transitions, is a complete misunderstanding of what problems SPAs solve. So absolu…

> But SPAs came about in the days of jQuery, not React.

(viper.pl 2000, philips.pl 2001 .. - are.. 'unreal' ??

'µloJSON': https://web.archive.org/web/20020702120539js_/http://www.vip...

historised chained htmls restart onerror: https://web.archive.org/web/20020402025320js_/http://www.aut... )

jQuery 2006, React 2013

Re: It's time for modern CSS to kill the SPA

#220

Post by danielscrubs »

cheema33 wrote: post #185
codingdave wrote: post #14

SPAs make sense when your users have long sessions in your app. When it is worth the pain to load a large bundle in exchange for having really small network requests after the load. Smooth transitions are a nice side effect, but not the reason for an SPA. The core argument of the article, that client-side routing is a solution for page transitions, is a complete misunderstanding of what problems SPAs solve. So absolu…

> ...if you shared that misunderstanding of SPAs and used them to solve the wrong problem, this article is 100% correct. Agreed. The article was a frustrating read. The author is an SEO consultant. SEO consultants likely have a heavy focus on marketing websites. Actual apps and not marketing websites do benefit significantly from SPA. Imagine building Google Maps without SPA. You can animate page transitions all you…

I 100% would like to see an MPA Google Maps.

Being able to come back to a webpage with previous directions? I think it would be glorious.

Post reply on HN