this post was submitted on 01 Nov 2025
103 points (100.0% liked)

technology

24221 readers
106 users here now

On the road to fully automated luxury gay space communism.

Spreading Linux propaganda since 2020

Rules:

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] Moidialectica@hexbear.net 20 points 3 months ago (4 children)

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

[–] Soot@hexbear.net 23 points 3 months ago (2 children)

If you're asking why Microsoft codes such overly complex, bloated and arbitrary mechanisms.. then you're about 20 years late

[–] robot_dog_with_gun@hexbear.net 16 points 3 months ago
[–] buckykat@hexbear.net 6 points 3 months ago

More like 30 and the original answer was "to keep people from running windows with other DOSes"

[–] hello_hello@hexbear.net 17 points 3 months ago

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.

[–] Awoo@hexbear.net 16 points 3 months ago

Using AI to write their code probably

[–] chgxvjh@hexbear.net 11 points 3 months ago

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.