News for hackers. Stuff that matters.
Re:It's time for modern CSS to kill the SPA by nromiun on Saturday July 26, 2025 @02:55AM (#44691977)
Lots of pushback here in the comments. But I can't think of the last time I enjoyed using an SPA website over a multi-page one. The initial loading feels delayed, the page scrolling feels unnatural and jarring (completely opposite of how a native app feels).

Also, one of my banks recently changed their old website to a new SPA one. And it is now completely useless. It can't load information in time, so most of the forms are empty. You can't even go back because it is an SPA. So I can only log out, log in and try again.

And it is not just one website. As I said I can't recall ever using a good SPA website. So yeah I can't wait until they are all gone.

Re:It's time for modern CSS to kill the SPA by kertoip_1 on Saturday July 26, 2025 @05:02AM (#44692582)
Yeah, the worst thing is when parts of the same application are under the hood different SPAs.

First example that comes to my mind: web version of ProtonMail. Going to settings feels like loading a completely separate website. Or OVH dashboard.

Re:It's time for modern CSS to kill the SPA by tossandthrow on Saturday July 26, 2025 @05:17AM (#44692638)
> But I can't think of the last time I enjoyed using a SPA website over a multi-page one.

You likely don't even notice that most of what you browse are SPAs.

The reason why there is pushback is because the article is straight up misinformation.

Re:It's time for modern CSS to kill the SPA by nromiun on Saturday July 26, 2025 @06:52AM (#44693055)
Actually the static address bar and the refresh button behavior makes it obvious.
Re:It's time for modern CSS to kill the SPA by tossandthrow on Saturday July 26, 2025 @07:38AM (#44693286)
What?

Most SPAs use full on routing. You can not distinguish refresh and address bar behavior between a SPA and static pages.

Furthermore, SPAs integrates perfectly with the browsers navigation stack.

Where does this bs come from?

Re:It's time for modern CSS to kill the SPA by nromiun on Saturday July 26, 2025 @07:44AM (#44693324)
Because less than 1% of actual SPAs use those things. Hell, look at HN's search page in the bottom if you want an example. You can load entire HN by the time it loads up and searches something.

Prefect example of the sufficiently advanced compiler argument.

Re:It's time for modern CSS to kill the SPA by tossandthrow on Saturday July 26, 2025 @07:50AM (#44693352)
HN's search is hosted on Algolia, and is not a part of the HN "App".

Hacker news is not a SPA.

Algolia's search is a SPA, but is perfectly utilizes the search so you can refresh a page (besides the error that they don't use page-based search), and is largely indistinguishable from a non-SPA site.

> You can load entire HN

You obviously have not context what so ever on how much content is hosted on HN.

Re:It's time for modern CSS to kill the SPA by nromiun on Saturday July 26, 2025 @07:56AM (#44693391)
Yes, I am well aware it is separate from HN. That is why I called it HN's search page.

You underestimate how fast modern internet is. With MPA website like HN there is no need to wait for any script to render first.

Re:It's time for modern CSS to kill the SPA by croes on Saturday July 26, 2025 @05:52AM (#44692811)
You think bad programming is restricted to SPAs?

If they botch the back button in an SPA they will botch other things in an MPA

Re:It's time for modern CSS to kill the SPA by nromiun on Saturday July 26, 2025 @07:03AM (#44693100)
But this bank's old MPA worked pretty well. By trying to modernize it they completely broke it instead.
Re:It's time for modern CSS to kill the SPA by maccard on Saturday July 26, 2025 @07:05AM (#44693112)
I’d put big money on it not being the same team that made the new app.
Re:It's time for modern CSS to kill the SPA by nromiun on Saturday July 26, 2025 @07:07AM (#44693128)
Probably. The old website was several decades old.
Re:It's time for modern CSS to kill the SPA by maccard on Saturday July 26, 2025 @07:05AM (#44693109)
The toupee fallacy strikes again here. Gmail, slack[0], Netflix and Spotify are top tier examples - they actually work. Most are true garbage though.

[0] I am firmly on the slack-performance-is-a-disgrace train, but their web client is a great example of a well done SPA - it’s miles better than the app other than notifications.

Re:It's time for modern CSS to kill the SPA by nromiun on Saturday July 26, 2025 @07:12AM (#44693146)
Gmail really? The same one that takes 10-20 seconds on 5G to even show the loading page? What is it doing in that time? Loading emails or downloading an AAA game? It is not just a one time penalty either, you reload and get the same loading page again.

Just a few days ago I had to get an OTP via email and it was completely frustrating. No indication nothing, just a loading circle. The old MPA version was much better.

Re:It's time for modern CSS to kill the SPA by kristopolous on Saturday July 26, 2025 @12:05PM (#44695093)
If it was built like we were in 1995, with tables and html 3.2 without JavaScript and just the old school inline attribute styles, it would be way more usable
Re:It's time for modern CSS to kill the SPA by nromiun on Saturday July 26, 2025 @12:16PM (#44695171)
It is also possible to create fast and functional websites on modern tech. But for some reason some people go completely crazy with Javascript.
Re:It's time for modern CSS to kill the SPA by austin-cheney on Saturday July 26, 2025 @08:52PM (#44698058)
SPAs do not exist to benefit the user. They exist to benefit the developer who writes them.
Re:It's time for modern CSS to kill the SPA by elendee on Sunday July 27, 2025 @01:23AM (#44699075)
I like the pushback because it means less competition in the native framework space
Re:It's time for modern CSS to kill the SPA by jeremy8883 on Sunday July 27, 2025 @03:01AM (#44699394)
if you're receiving jarring page scrolling, it is not the fault of the spa, it's something else at play. it is not they typical spa experience.

if the back button doesn't work, the site was poorly programmed, since any routing library will handle that for you.