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

321–330 of 516 posts

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

#321

Post by tossandthrow »

nromiun wrote: post #301
tossandthrow wrote: post #279

Earlier quoted context omitted.

> 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.

Actually the static address bar and the refresh button behavior makes it obvious.

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

#322

Post by nromiun »

tossandthrow wrote: post #321
nromiun wrote: post #301

Earlier quoted context omitted.

Actually the static address bar and the refresh button behavior makes it obvious.

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?

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

#323

Post by Quarrel »

al_borland wrote: post #298
Quarrel wrote: post #281

Earlier quoted context omitted.

> They are either the worst developers in the world or it is not simple. Or they have a good reason to not do it (in some PMs mind). At a guess, resetting the view, and displaying the nearest Domino's Pizza sponsored highlight pin on the map, could be one of them.

My biggest gripe with Google Maps is when I pan to a specific area, hundreds, or even thousands of miles from my current location, then search for something like “restaurants” and it pans me back home and searches there, so I then have to go find my distant location again and click the search here button. If this is an intentional choice, all in an effort to show me more local ads… ugh. I really hope this isn’t the c…

I hate that too. Even when it is just across the one city, it is a major pain in the ass.

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

#324

Post by tossandthrow »

nromiun wrote: post #322
tossandthrow wrote: post #321

Earlier quoted context omitted.

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?

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.

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

#326

Post by nromiun »

tossandthrow wrote: post #324
nromiun wrote: post #322

Earlier quoted context omitted.

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.

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.

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

#327

Post by nsonha »

what a nonsensical title, clearly written by people that only program skins around applications instead of applications themselves. CSS and SPA do not even solve the same problem.

I'm sure there exist (foolish) efforts to make CSS somehow able to do some UI logic, but that is never a good idea. CSS is a poorly made/overly complex spec that deserves to die. It's too late to make that argument unfortunately, but to want even more of CSS in the modern web stack is kinda lunatic.

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

#329

Post by mexicocitinluez »

yoz-y wrote: post #46

For me the promise of SPAs has nothing to do with fluidity and all to do with having a separate data API and separate frontend (that can be native or web or both) That’s why I don’t like SSR mixed with client side rendering. Either do a website or an app.

Not just for you, but for most people.

The author of this article is making shit up to justify writing an article where they can show of their CSS skills. It's lame and dumb.

Post reply on HN