What makes me laugh super hard is all these vibe coded apps come out and for some reason the AI is really good at making it completely kosher on Linux. Like for instance, those slop coded Adobe apps have flawless wayland support and resize with no flickering or swapchain redraw funkiness it blew my mind honestly.
Having heavily used AI to write a lot of really finicky stuff, yeah, more than once I've said "well, uh . . . can you go download the KDE sourcecode and figure out what's causing this?"
"Sure! I'll give that a shot."
and twenty minutes later it's hand-analyzed the entire failure chain and has a clever workaround.
. . . Of course, given how good it is at reverse engineering, this is starting to be less restricted to open-source. I haven't yet asked it to go decompile Windows, but that might happen at some point.
AI doesn't have to bother with learning obscure documentation of something devs wouldn't learn as a career investment as the market is so marginally low.
I'm generally against vibecoding and a majority of AI use in software development (generally produces unmaintainable codebases). One thing I will die on the hill of AI for is using it to deal with the nightmare that is documentation. It's ridiculous the amount of time I've spent in my life reading documentation for a library or program only for it to be completely wrong or superseded by a newer version/removed. Being able to point a research assistant at the git repo and asking it questions has been a godsend.
I mean, in this case, he's using it to search through existing documents, which is something that LLMs apparently actually do pretty well without hallucinating too much.
Yeah, or migrating things to new versions of libraries: hey is it safe to upgrade to major X version to deal with this vulnerability warning? Almost always is on point as it can analyze the api usage in the codebase and plan the migration if there's any incompatibility
That API-usage analysis is genuinely handy for planning a major bump. Worth separating two jobs though: the vulnerability warning and the major upgrade. The CVE fix itself is usually a small, known patch, and vendors exist who backport it onto the version you already run, so you clear the warning without the migration risk. The big bump then becomes its own scheduled project. Which package throws the warning?
To be fair, many software are legacy software that have been updating things for decades with all kinds of workarounds. New software can just drop the baggage of porting old code and just use libraries that were already made to work with wayland.
24
u/Floturcocantsee 1d ago
What makes me laugh super hard is all these vibe coded apps come out and for some reason the AI is really good at making it completely kosher on Linux. Like for instance, those slop coded Adobe apps have flawless wayland support and resize with no flickering or swapchain redraw funkiness it blew my mind honestly.