It’s usually vastly easier to verify an answer than posit one, if you have the patience to do so.
I'm envisioning a world where multiple AI engines create and check each others' work... the first thing they need to make work to support that scenario is probably fusion power.
In University I knew a lot of students who knew all the things but "just don't know where to start" - if I gave them a little direction about where to start, they could run it to the finish all on their own.
I have been using AI to write (little, near trivial) programs. It's blindingly obvious that it could be feeding this code to a compiler and catching its mistakes before giving them to me, but it doesn't... yet.
I ask AI to write simple little programs. One time in three they actually compile without errors. To the credit of the AI, I can feed it the error and about half the time it will fix it. Then, when it compiles and runs without crashing, about one time in three it will actually do what I wanted. To the credit of AI, I can give it revised instructions and about half the time it can fix the program to work as intended.
Thanks. In the past I have worked in Slackware, and even had Gentoo on my home system for a couple of years, but otherwise I've been fully saturated in Debian and its children - so that's my "comfort zone." I used to like KDE, but drifted away from it when I got a 4K screen notebook and KDE hadn't figured out resolution scaling yet, while Ubuntu/Unity had. I never quite warmed up to GNOME, but definitely have done my time with it. XFCE has matured enough for me to daily drive it without too much pain now, and I love the ways it can be de-featured (don't want a launcher bar? Don't run it, nothing else breaks.)
Server-side, I have been filling my Raspberry Pis with Docker containers for a while now... it's not completely alien, but I do kind of tend to "set it and forget it" when it comes to container deployments.
The one "good" thing about containers is that you keep your DLL-like mess localized. Just one or a few related apps run in the container and if they want / need some weird library version, they can have it without breaking other things.
The thing that grinds my gears is when I'm doing an apt update and then it goes off to check on the snaps and drags the process out a lot longer. It doesn't help that they're slower to load the apps too. Then there's the additional attack surfaces to accumulate more CVE reports (and more out of date library versions on your system begging for a security patch...) Mostly, I just purge snap support from Ubuntu these days - but for people who don't notice / mind such things, you do you - maybe they'll eventually improve the lightweight container system until the rest of us don't notice it either.
I wouldn't say I have had a problem with snaps or flatpacks either. I uninstall all snaps first thing when I install recent Ubuntu versions, and I have never messed with flatpacks, so... no problems.
And they are still, in my experience, slow to load, a cumbersome addition to the update process, and often un-necessary.
Don't get me wrong, if you're in a tight spot and can't make two significant software packages work in a distribution due to conflicting library version requirements... some kind of lightweight container solution is attractive, expedient, and better than just not supporting one of the packages. But, my impression is that a lot of stuff has been moved into flatpak / snap / etc. just because they can. I don't think it's the best, or even preferred, way to maintain software - for the desktop environment.
(Returns to checking on his Docker containers full of server apps on the R-Pi farm...)
That's what happens when you have Intel inside ;o)
(Yes, yes, I know, it's the whole binary based floating point thing, not just Intel, although my Atari 800 BASIC interpreter implemented floating point in BCD, so it didn't have that issue.)
It has also led to me saying “I fucking told you so” more than a few times.
I have had several situations where I didn't even have to give knowing looks, everybody in the room knew I told them so six months ago and here it is. When that led to problems working with my leadership in the future (which happened more often than not), that was a 100% reliable sign that I would be happier and more successful elsewhere.
Stack Exchange coding is 5% finding solutions to try and 95% copy-pasting those solutions into your project, discovering why they don't work for you, and trying the next solution on the search list.
I just use A.I. to simplify the tedious data gathering and organizing.
If you're conscientious, you check AI's output the same way a conscientious licensed professional checks the work of an assistant before signing their name to it.
If you're more typical... you're at even greater risk trusting AI than you are when trusting an assistant who is trying to convince your bosses that they can do your job better than you.
As useless as a cubicle farm full of unsupervised workers.