32 karma · joined November 9, 2026
I don't particularly care about copyright or whatever ethical arguments yo may come up with -- I write code mostly for money, as do my competitors -- if you can figure out a way to stop them from using AI, I'm fine with not using it either. I'm fairly skeptical you can close Pandora's box though.
That aside, we may see more software going in a source-available direction -- either that or full cloud. Up until now being closed source was a competitive advantage, but now it's trivial to clone even fairly huge software suites, so that's less of a factor.
Having the source may also become a bigger advantage for regular users than before -- given they can now vibecode extensions/plugins, or customize the software more than what a config would personally allow. this probably wings the calculus away from a Photoshop-style license, and closer an Unreal Engine-style license.
Either that; or everything goes full cloud of course.
In the long run I also imagine this sort of thing being something someone does once per phone model and uploads it.
They already have to deal with the fact that if they're shipping binaries that they actually want to work, they have to compile their own compiler, libc, libc++, Xlib, static link everything, don't touch anything the system provides, dynamically load the things you can't get around, test multiple .so paths for different distros, etc, etc, etc...
Now, on top of that, they're being asked to support a second completely different Window System layer, that an even smaller percentage of people use (and who mind you all also run Xwayland).Unlike X11, Wayland doesn't have one de-facto standard implementation, and the spec doesn't define anything - some common functionality is provided through different incompatible extensions, and some common functionality is not supported at all.
I was trying to set up my VR headset for Linux a few week back and I saw [1]. Feature disparity is so bad that Valve, the biggest corporate proponent of the Linux desktop, concluded they just can't support SteamVR on the biggest desktop environment, and basically tells you to switch to X or another compositor.
That's without going into the technical insanity of the protocol, like using sockets and a client-server architecture for something that can't actually run over the network, because Linux developers just can't envision a form of IPC that doesn't pass through the kernel and take 2ms, or the fact that the standard client library can't be static linked by default without you rewriting its build system.
If one day X11 dies, it will be because Linux has settled on the Win32 API, not Wayland.
[1] https://help.steampowered.com/en/faqs/view/18A4-1E10-8A94-3D...
Me: OK, what should I do?
Me: OK, how do I contact INAH? How does the reporting process work?
Me: OK, please do the report.
computer what do? computer help. computer do thing for me. computer post blog please. computer post to HN for me.If this is what people's sessions look like, no wonder everyone is so paranoid about getting replaced.
I'd be interested to see the first one that makes >0$ on SteamSalesBench.
I'm having it rewrite an old system, and it keeps sweeping known bugs and incompatibilities in its new implementation under the rug, seemingly with the hope I won't find them. It also has a tendency to do about 50% of what I specify in the prompt and call it a day, and respond with "Here's what I did", without mentioning all the things that I requested that it did not do, not even as a TODO.
I may try running the same exercise with Opus 5.5 too, but so far I'm seeing it take shortcuts that I don't believe any of the other SOTA models would have.
Frankly, so far this model feels a bit malicious.