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

91–100 of 516 posts

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

#91

Post by kassner »

kassner wrote: post #79
chaps wrote: post #29

Earlier quoted context omitted.

Is this true? When I think of old SPAs I think of java apps running in a browser. Those are definitely older than jQuery. (I love this silly site for downvoting this question.)

ExtJS came about in the late 00s, and it was possible to build SPAs with it, overlay/draggable windows, and had powerful grid/form components.

https://extjs.cachefly.net/ext-3.4.0/examples/ unfortunately most of the data examples don’t work, but I believe everyone browsing the web back then remembers this blue tinted interface.

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

#92

Post by afavour »

threatofrain wrote: post #63
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…

> Startups and SV jerk each other off by promoting each other (think affiliates). None of it means shit. No, this is FB ceding the battle. They absolutely didn't want this. They dropped CRA because social media celebrities were shitting on CRA. Dan Abramov had to do a complete 180 in a single day, after writing a long thoughtful essay in defense of CRA.

Wars, battles, personalities on social media… I don’t want to sound too much like a grouchy old man but these frameworks are tools. Nothing more than that. I can’t understand why anyone would become emotionally invested in any of them.

When starting a project the right move to examine what best fits your project, not which one was recently victorious in a war. I’ve grown to dislike React because I see it being abused so often for a site where it isn’t necessary. There are plenty of projects where it is necessary too, but that’s not universal.

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

#93

Post by ninetyninenine »

>The reason SPAs became the default wasn’t because they were better. It was because, for a while, they were the only way to deliver something that felt fluid – something that didn’t flash white between pages or jank the scroll position.

This was NOT the reason why.

SPAs are better because it offloads as much processing as possible to EDGE cpu's. The idle compute among all users aggregates to a massive amount so might as well use it and minimize html construction and routing on the server side.

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

#95

Post by karaterobot »

A lot of people are responding with other technical considerations that may lead you to consider using an SPA pattern. But, note that the article is about responding to the stakeholder's request that it should 'feel like an app', and his point is that you can make it feel like an app without being an SPA. Non-technical stakeholders rarely bring up deep technical considerations, they almost always talk about what something should feel like. So, I think his argument, while unlikely to work on anybody, is valid.

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

#97

Post by throwawaylaptop »

dzhiurgis wrote: post #73
ec109685 wrote: post #59

Earlier quoted context omitted.

In almost all cases the back swipe in the spa resets you to the top of the page, navigating out of the app and back in doesn’t work, etc. It’s really hard to build a multi page spa that feels good.

Never thought about scroll position (tho SPA I’ve built recently I think does it ok). How do you solve it?

I'm a self taught PHP/jQuery/bootstrap guy with a small saas. I handle page scroll position by literally saving it into some session data cookie and when you go back I check where your scroll was and I fix it for you. I'm not a genius or skilled... But I cared so I did it.

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

#98

Post by threatofrain »

ivape wrote: post #69
threatofrain wrote: post #63

Earlier quoted context omitted.

> Startups and SV jerk each other off by promoting each other (think affiliates). None of it means shit. No, this is FB ceding the battle. They absolutely didn't want this. They dropped CRA because social media celebrities were shitting on CRA. Dan Abramov had to do a complete 180 in a single day, after writing a long thoughtful essay in defense of CRA.

You are in your own little universe. Social media celebrities shitting on React? I don't even want to enter your world. "Bro, you should see the celebrities shitting on React" Like WHO!? What developer celebrity, what universe have I been missing out on? Anyway, I do love me a good ol' fashioned "fuck SPAs, back to HTML" punching bag post on HN. It's always the same discussion over and over.

We're living in the same universe. When you read the documentation you see something. I'm just giving the story behind it.

You don't need generic answers about people wanking each other off for "think affiliates".

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

#99

Post by gerdesj »

"... someone says the words. A CMO. A digital lead. A brand manager. ... it’ll be an SPA."

Why not spell out CMO and SPA and a civilian such as myself will not have to toddle off and dig out a search engine?

If you are going to get all assertive and pissed off, please be inclusive too.

Post reply on HN