This fucking vibe coding thing is going to destroy the already declining software engineering standards of these companies.
technology
On the road to fully automated luxury gay space communism.
Spreading Linux propaganda since 2020
- Ways to run Microsoft/Adobe and more on Linux
- The Ultimate FOSS Guide For Android
- Great libre software on Windows
- Hey you, the lib still using Chrome. Read this post!
Rules:
- 1. Obviously abide by the sitewide code of conduct. Bigotry will be met with an immediate ban
- 2. This community is about technology. Offtopic is permitted as long as it is kept in the comment sections
- 3. Although this is not /c/libre, FOSS related posting is tolerated, and even welcome in the case of effort posts
- 4. We believe technology should be liberating. As such, avoid promoting proprietary and/or bourgeois technology
- 5. Explanatory posts to correct the potential mistakes a comrade made in a post of their own are allowed, as long as they remain respectful
- 6. No crypto (Bitcoin, NFT, etc.) speculation, unless it is purely informative and not too cringe
- 7. Absolutely no tech bro shit. If you have a good opinion of Silicon Valley billionaires please manifest yourself so we can ban you.
more like destroy our entire society, can't wait until it's in charge of like water treatment or power companies and it does a little fucky wucky
You'll be happy to hear that manuals for, for example, nuclear reactors are already being translated by AI.
New bug found in reactor: when using Windows SCRAM Manager to damp reaction by inserting the control rods, the rods are raised instead.
You're in luck. For the meantime, a lot of these embedded systems are still running operating systems like Windows XP, or Windows NT 4.0.
this what they mean about the dangers of "AI" lol. that everything will use it despite it being dogshit.
Hey, maybe that means more people can have a shot at learning coding. Show up, and be hailed as a genius.
Thanks AI bros for demystifying tech.
They have good talent. The problem is them pushing unrealistic timelines on devs which one has to meet if they don't want to get laid off. And to meet these timelines they have no choice but to use AI code.


I'm just wondering, what possibly could've happened to cause this specifically to terminal manager but not any other app? Were they trying to make it always stay on in the background? Why though, that's so useless for something that already opens fast
If you're asking why Microsoft codes such overly complex, bloated and arbitrary mechanisms.. then you're about 20 years late
retvrn to XP
More like 30 and the original answer was "to keep people from running windows with other DOSes"
The neat thing is that it's all proprietary and we'll never know. Given how everything on windows is so tightly bundled together (pejorative). It might be a library dependency thing that didn't sync with task manager.
Using AI to write their code probably
Were they trying to make it always stay on in the background?
I hate when programs do that. If I wanted it to run in the background, I'd hit the minimize button.
teleports behind myself Nothin' personal, kid.
Once you reach into the billions of installs you might consider doing a little QA.
Microsoft using their users as guinea pigs has always been a thing. Hearing how windows users are terrified of updating their computer is just wild to me because on Linux every update is like a Christmas come early.

Now more than ever: Learn to hack, Learn to quadcopter.
If it achieved AGI - to close Task Manger wouldn't it demand one billion dollars?

Oh glorious innovation! Now integral tools for your OS have all the excitement of finding the right X button to close ads on sketchy-ass piracy webistes 
the windows UX is where you are periodically get a random encounter to solve a puzzle of rubix cube complexity, except it's using the user interface and it may not have a solution. at any point you can bypass the random encounter puzzle by hard booting the system and losing whatever unsaved work was still open.
i think one of the things that finally got to me was just how long a windows reboot was taking. not just to get to the desktop, but to be able to do whatever it was i was at the computer to do. and every time i couldn't solve the random windows puzzle, i was doing it. staring at the dumb spinning dots, waiting.
by contrast, my linux systems went from off to desktop in about 47-51 seconds.
I miss my Amiga 1200 with an external hard drive and 68030 accelerator card clocked at a whopping 50 MHz. A cold boot took around 8 seconds before the system was usable. Hell, even booting from floppy took no more than about 38 seconds. (Yes, I timed this shit, and yes, I still remember it from 30 years ago.)
what about alt+f4?
taskkill /f /im taskmanager.exe
had to learn that one when excel leaving background processes open, using about 20MB and using all of the ram on the PCs at work. it beats a restart.
when SSDs were becoming more widely available around 2012 if you bought one and put your windows install on it you could boot in like 10-12 seconds. Now we have broke task manager.
Clippy maximizer