News for hackers. Stuff that matters.
Re:Actively exploited sandbox RCE in all Chromium versions by DANmode on Friday September 04, 2026 @11:18PM (#49572789)
> SPAs will be slow no matter what.

Uh…no?

You’re presumably talking about specific terrible prebuilt frameworks - not someone building a nice vanilla SPA.

Re:Actively exploited sandbox RCE in all Chromium versions by grishka on Friday September 04, 2026 @11:53PM (#49572933)
At this point SPA pretty much implies React. But even if you optimize everything the best you could and avoid any third-party runtime dependencies, it's still going to be significantly more work to make API requests and do client-side rendering vs just rendering HTML server-side.
Re:Actively exploited sandbox RCE in all Chromium versions by dvdkon on Saturday September 05, 2026 @04:09AM (#49574279)
Not always. Consider an SPA that connects via WebSockets and streams in data, adding points to a chart. The JS-less alternative would be refreshing an SVG or even the whole page once a second. The SPA is clearly more efficient here (unless someone screws it up badly).
Re:Actively exploited sandbox RCE in all Chromium versions by grishka on Saturday September 05, 2026 @04:28AM (#49574418)
I wouldn't consider that an SPA at all, it's just a page with an interactive element. An SPA is something that renders everything client-side and uses a generic client API to talk to the backend. A telltale sign of an SPA is that the first thing you see when you open it is some sort of loading indicator instead of the actual page you're visiting.
Re:Actively exploited sandbox RCE in all Chromium versions by DANmode on Saturday September 05, 2026 @10:41AM (#49576994)
No, the telltale sign of a SPA is that it’s an app that’s a single fucking page, lol

Please stop changing the definitions of explicit words and phrases - to anyone reading this!

Re:Actively exploited sandbox RCE in all Chromium versions by preg_match on Saturday September 05, 2026 @02:27PM (#49579287)
Right but the implication of a SPA is that it’s an application which has many logical pages, but only one real page. The logical pages are constructed by dynamically updating the DOM using JavaScript. As opposed to navigating to a new, server-provided page.

For example, a search function. For a MPA, each search query would be a new page. For a SPA, each query is a new logical page, served on the same real page.

Technically yes, a SPA may have minimal client side rendering. But then it’s not doing much of anything at all - it’s just a site. When people say SPA, they typically mean an application with client side rendering.

Re:Actively exploited sandbox RCE in all Chromium versions by DANmode on Saturday September 05, 2026 @03:47PM (#49580030)
> it’s just a site

sigh

…does someone else want to finish this up?

Re:Actively exploited sandbox RCE in all Chromium versions by preg_match on Saturday September 05, 2026 @04:22PM (#49580307)
This reply means basically nothing to me or anyone.

To expand on what I mean, if the implication isn’t obvious: a SPA with no client side rendering is just a single HTML page. It’s a document, not an application.

So SPA naturally implies client side rendering.

The difference between a SPA and MPA isn’t the amount of pages, they both have about the same amount of logic pages. It’s about where those pages are rendered. Dynamically on the front end, or on the back end.

EDIT: okay okay to expand, my website has a contact form. With JS enabled, the form submit displays a little box that says “thank you for submitting”. With JS disabled, it navigates you to a “thank you for submitting” page.

Both are the same logic page, they have the same function. One page is just rendered client side, and one server side. Most websites or applications are hybrids. There’s very few true single page applications, and very few true multi page applications. Most SPAs have multiple real pages for different things. Most MPAs combine multiple logic pages into one real page.

Re:Actively exploited sandbox RCE in all Chromium versions by DANmode on Saturday September 05, 2026 @07:19PM (#49581697)
Single HTML files / pages can be fully-featured, full-purpose-fulfilling applications.

> Most websites or applications are hybrids.

and some are emphatically not.

But…where were you going with that?

Re:Actively exploited sandbox RCE in all Chromium versions by preg_match on Sunday September 06, 2026 @02:36PM (#49589464)
The features of HTML are still greatly limited. You can’t really create applications with just one HTML page and no client-side rendering. You can play a video, sure, but that’s not an application. You can also do magic with CSS but that’s an experimental fun thing, not a thing people actually do.

As soon as you, say, use JS to update the DOM or a canvas, I consider that client-side rendering. That you can do, and that would be a SPA.

But I’m curious, what are some examples, even hypothetical, of applications consisting of one HTML page? I don’t think I’ve ever seen it.

Re:Actively exploited sandbox RCE in all Chromium versions by DANmode on Sunday September 06, 2026 @11:47PM (#49593651)
You can inline the following in one HTML page:

CSS (.css) JavaScript (.js) Plain Text (.txt) HTML (.html) SVG (.svg) Raster Images (.png, .jpg, .jpeg, .gif, .webp, .bmp) Audio (.mp3, .wav, .ogg) Video (.mp4, .webm) JSON (.json) PDF (.pdf)

plus bring in other source resources as needed.

To answer your question:

The installer for GrapheneOS / Google Pixel phones is an “SPA” (or “webapp”).

I’ve seen bespoke fitness trackers of all kinds,

appliance control apps,

budget and pace-tracking stuff,

basically all of what computer programs used to do - before we started dynamically loading a ton of extra stuff onto the screen that nobody needed to do the task they came to do.

Re:Actively exploited sandbox RCE in all Chromium versions by preg_match on Tuesday September 08, 2026 @05:41PM (#49617501)
Right, but if you’re dynamically changing the HTML from JS, like the graphemeos website does, then that’s client-side rendering, which is my whole argument. Embedding the JS in HTML makes zero difference, it’s the same thing.

So, they are truly inseparable IMO. You can’t have a SPA without some amount of client side rendering, your example demonstrates that. So, what makes a SPA a SPA is the rendering. A SPA is “single page”, but only in literal meaning. Logically, every SPA is many pages, you just render them purely client-side.

Re:Actively exploited sandbox RCE in all Chromium versions by DANmode on Saturday September 12, 2026 @06:02PM (#49677666)
Almost every major website you interact with daily relies heavily on client-side execution to some degree.

and none of this seems to have anything to do with the frontend being a single page.

Re:Actively exploited sandbox RCE in all Chromium versions by grishka on Saturday September 05, 2026 @06:33PM (#49581369)
By that definition, Smithereen, my fediverse server software, is also an SPA, since it does what I call "ajax navigation" on desktop, so that the notifications websocket doesn't get disconnected and reconnected every time you click a link. It's technically a single page that gets most of its content replaced at runtime when you click a link, after all, right?
Re:Actively exploited sandbox RCE in all Chromium versions by DANmode on Saturday September 05, 2026 @07:17PM (#49581678)
Yes.

Could you point out where you think the gotcha is? I can taste the tone.

Just because a bunch of engineers applied implicit meaning that didn’t exist to a very literal phrase for a few years doesn’t make it correct.

Doesn’t make webapps inherently bad.

Doesn’t make SPAs bad.

Re:Actively exploited sandbox RCE in all Chromium versions by DANmode on Sunday September 06, 2026 @01:14AM (#49583523)
> At this point SPA pretty much implies React

At this point, app pretty much implies React - ask an LLM for an app and see if that’s not what you get.

Re:Actively exploited sandbox RCE in all Chromium versions by realusername on Saturday September 05, 2026 @03:40AM (#49574106)
I've never seen an SPA which scales properly and doesn't become a bloated mess, maybe that's possible but it's definitely harder to make it work than using traditional server side template rendering
Re:Actively exploited sandbox RCE in all Chromium versions by DANmode on Saturday September 05, 2026 @03:52PM (#49580074)
Plenty of app usecases don’t need to “scale” - immediately or ever!
Re:Actively exploited sandbox RCE in all Chromium versions by realusername on Saturday September 05, 2026 @04:00PM (#49580145)
That's a good point but you never know that from the start, "this app won't scale well" is a hard sell for a new project in my opinion
Re:Actively exploited sandbox RCE in all Chromium versions by DANmode on Saturday September 05, 2026 @10:14PM (#49582667)
Especially today, single-user stuff, especially in categories of things like health,

especially when you’re writing your own stuff,

that’s when you know from the start that scaling doesn’t matter! =]

Related, and more powerful than my comments in this thread are going to be:

https://www.robinsloan.com/notes/home-cooked-app/

Re:Actively exploited sandbox RCE in all Chromium versions by realusername on Sunday September 06, 2026 @01:34AM (#49583620)
I don't only mean "scale" in terms of users but also scale in terms of features.

So you have to guarantee that your product will stay low users and low features forever or spend a very high effort to try to partially overcome that block when you change your mind.

And guaranteeing that it will stay low features is much harder than low users I think.

In exchange for that you get a better talent pool for recruiting but does that matter if your product has to stay low scale anyways?

Re:Actively exploited sandbox RCE in all Chromium versions by DANmode on Sunday September 06, 2026 @11:45PM (#49593643)
Or you have to distribute your code in such a fashion, and structure your business model in such a way, that “scale” doesn’t require you doing things that have nothing to do with providing the feature set (most SaaS).
Re:Actively exploited sandbox RCE in all Chromium versions by realusername on Monday September 07, 2026 @02:24AM (#49594601)
I'm currently working on a SaaS at my company and we have a lot of issues because of the SPA, I estimate we spend around 5% at least, maybe 10% of the workforce just on SPA complexity.

It can work for some SaaS but if you stay low employee count, low users and you have a core feature used everywhere in the whole product and nothing else

Re:Actively exploited sandbox RCE in all Chromium versions by DANmode on Monday September 07, 2026 @04:34AM (#49595602)
What’s the stack? Is it being used even sort-of in the right place / way?

Feels like a glaring omission =]

Re:Actively exploited sandbox RCE in all Chromium versions by realusername on Monday September 07, 2026 @05:11AM (#49595921)
The stack is Rails / React SPA for the frontend.

> Is it being used even sort-of in the right place / way?

It's a SaaS where users are mostly always logged-in, kind of an app so you would think it should work from the outside.

I think these are the full requirements I would put for a good SPA experience:

- low users

- low number of features / or a single main feature reused in different ways

- low number of employees

- it's an app and not a website

- you don't have any users living in remote places / poor internet connection

- users are all using modern browsers and can be asked to switch to another one if needed

And I think in my company we only have one of this list, making it painful.

Re:Actively exploited sandbox RCE in all Chromium versions by DANmode on Monday September 07, 2026 @03:29PM (#49602026)
If anyone wants to show up and talk non-React anything,

at any point,

I’ll be checking back around later!

Until then: just talk smack about React!

None of these things you listed are critiques of single-page apps (SPA).

Re:Actively exploited sandbox RCE in all Chromium versions by realusername on Monday September 07, 2026 @05:31PM (#49603184)
I don't have a final opinion on the subject, it's just the results I witnessed after a long time in the industry. The ones I've seen with Angular suffered from the same issues.

I'm sure counter examples of well managed SPAs do exist somewhere, it's just that it seems much easier to do the wrong thing compared to a traditional stack. This is why I'd not advise for it unless you have a very good reason.

The good stacks should make the good choices the natural way to do things, again my opinion.