vga1

I used the net much more intellegently back when it was paid by the minute. But it would be hard to go back to that.

> I would almost bet that AI would warn about that.

Exactly. If they had a review process. Which they didn't, at least for that change.

https://xkcd.com/1200/

That remains to be seen. The whole concept is still in its infancy. An AI reviewer should have caught these issues when they were PRs.

But you see, it wasn't even a PR. It was just DHH making a straight up commit on the main branch (as far as I can see). With a message "Do all the additional Docker configuration needed". Was it even AI-assisted? At least the commit message wasn't, AIs write smarter commit messages than that.

I said on my earlier comment that DHH and AI get ridiculed automatically because people hate both. That doesn't mean that the ridicule isn't always justified.

https://github.com/omacom/omarchy/commit/25799ee91f54c35e6d3...

Bun.

Yes, I know. That is quite juvenile.

Even worse. They don't even have AI review them. I fed the commits that introduced the problem to a few frontier models and they saw several problems, including the aforementioned security problem. Even Mistral saw it. I did have to instruct all models to look for security problems, though, but still.

It's not that we shouldn't use vibecoded distros. It's that we shouldn't use badly vibecoded distros with shitty or non-existent processes.

People hate DHH and AI, so whatever he does or what is done with AI is ridiculed.

If only their stuff could reliably run Linux on the release day.

Number go up

Seems like they just released 1.4 though.

Are the Rust programmers who suffered from memory leaks through reference cycles in the room with you right now?

Pro architect tip: Usually foundation goes below the thing you're building.

Who cares?

What are the standards for determining that?

The most obvious benefit Rust can give them is being safe from memory leaks. This is hardly controversial: it has been a Zig design choice that memory leaks are the developer/user's responsibility. They have already demonstrated to have fixed several of those [0].

Marketing-wise, it has been an obvious success. Dunno if that matters.

[0] https://bun.com/blog/bun-in-rust

This isn't a Linux problem, per se. I've been using Linux since 1996.

It's because you're using XFCE, which might be one of the last desktops to adapt to Wayland. Mint has similar problems, they have also dragged their feet. So the tech stack you have selected has pretty much maximum problems.

You need to embrace Wayland and Pipewire, not avoid them. Linux has never been about being a luddite, rather the exact opposite.

What do you mean? That is reported to be literally what she said.

Like AOC has said (and Mamdani apparently supported), "Woke 1.0 was crazy".

https://www.axios.com/2026/08/12/aoc-democratic-socialists-2...

Twitter's acquisition seems to me like an attempt to acquire the most efficient propaganda tool on the planet.

Makes sense to deploy counterpropaganda. They haven't been doing great online.

I think it's possible, but probably beyond my capability of imagination, so I cannot give a satisfying answer beyond this.

Obviously the right thing to do. How to reliably do it might be a bit difficult, but fortunately a ban doesn't have to be 100% effective to be beneficial.

There is going to be something that would not have existed without LLM because there wouldn't have been enough resources to create it before. Probably already is. Some of it will be amazing, although most of it probably not.

Example: Qobuz has no official Linux client, but there's https://qbz.lol/ which it seems to me is mostly vibecoded. It's not perfect, but it works pretty well and can do some fancy stuff like bit perfect DAC passthrough up to 192kHz/24bit.

I don't know, sometimes programming language choices seem to be in the realm of theology, not computer science or engineering.

What is more hurtful than somebody else making wrong religious choices?

I'm on the same page with you that their AI stance is probably harmful for them -- but I think they wrote those as a reaction to the contributions from Bun and others. So your implied timeline is not entirely correct.

I think the mistake people are making currently is that they publicize stuff way too early. I.e. they make a prototype and then put that out there. Possibly with a full product page and all.

People did this also before LLM, but the difference is that now the prototype is a fully functional product in the technical sense whereas before it was little more than a glorified Hello World. The human effort and calendar time used remains roughly the same.

There's gonna be amazing products made with LLM, but it'll take some time. Not as long as it did before, but still significant time.

Good old "fire everyone then fire yourself" style of downsizing.

The sad part is that my previous robot (iRobot model from 3 years ago) was better at this.

Please oh please try to make Kärcher adopt your stuff. Even their latest premium cleaning bots are hopeless when they don't know where they are, even when I tell them where they are.

Or, I don't know, make your own vacuums.