rudedogg

> because it wasn't actually running PHP

Yea and no, I mean it was an even worse setup than typical, probably because the person setting it up didn’t have php experience or used an LLM that misinterpreted “route requests from nginx to php” or something too literally and set up a hacky solution.

But my impression isn’t that they set it up in some cheeky way to avoid exploits, it looks like they just asked for nginx to be in front.

And is “hacked in two hours” fair if they had to make it easy for people because their noob setup ended up not being exploitable?

Let me know if my read of what happened is wrong.

I don't see how Canvas or WebGPU is any different. People want a way to write high-performance UIs without all the complexity/legacy of the DOM. It makes everything more difficult, and because it makes things easier for browser developers isn't a valid justification to make the user experience worse. The users should drive the technology. I'm sorry this architecture you built almost 30 years ago isn't adaptive enough to meet the needs of your users. Instead they should create a new one for this use case (GUIs/applications) and keep it focused on documents.

> isn't adaptive enough to meet the needs of your users

I imagine if this conversation continues this will be quoted and argued against. My point is that it's not working well. People find workarounds to do amazing things with the browser, but they shouldn't have to. Give developers what they've wanted for 15 years. The various committees and working groups keep missing the mark, by a lot. See WASM, WebGPU shader language, etc., etc.. I'm sure it's more complicated than I realize, but if all you do is fail and disappoint, maybe your governance model and the people involved need some adjustment. Is anyone happy with WebGPU? Is anyone happy with Web Components?

/rant

> Which GUI toolkits over internet do you refer to?

My point is there is no GUI toolkit for the browser and there should be. They should stop trying to morph the document object model into a platform for delivering applications, let it do documents, and give us something else/new. It'd also be the proper path to the new thing having accessibility support. Instead people raw-dog the GPU for UI and you get no screenreader support.

What they're doing here is a half-assed attempt: letting people draw but using the DOM for accessibility. The worst of both worlds I guess?

Our only hope is for AI to supplant screen readers, and then we can just ship WebGPU apps.

Look at GUI toolkits going back to the 90’s. The DOM and web development were an accident of history

The problem with doing apps on the web is the DOM. It’s wild how much complication browsers will add instead of just adding a new UI rendering method/substrate that doesn’t inherit 30+ years of legacy (remember web apps didn’t even exist for like 15 of those).

The DOM is a slow annoying pile when you want to make actual applications.

Also, the language just isn’t suited well to making games. Can anyone point me to a successful Rust game? Bevy game?

Also, the threat to privacy. If I turn on iCloud Private Relay I get bombarded with CloudFlare captchas. It’s so annoying I sometimes turn it off just for that reason.

Having some all knowing entity running the internet has a lot of downsides.

DaisyDisk is such a nice app. I just checked and I purchased it over 11 years ago.

They still update it, it works perfectly, no version 2.0 forced obsolescence. Just a nice, reliable tool.

Agreed. I wish they would have thrown in a "guardrails to stop me, but mostly my competitors" so the public would think about that possibility more.

Thanks for the info, I didn’t know that about the 5hr limit

Sol is their middle model. Luna is smallest. And Astra is big, their Fable equivalent.

I think the market didn’t react like they expected and now they’re like “jk”.

And I don’t think any pacing is/was intentional. They’de release skynet if they could and the stonks went up