This week on Windows...

4 months ago by FoxtrotDeltaTango to c/programmer_humor

cross-posted from: https://lemmy.world/post/48711326

https://www.live-feeds.com/...

orca 58 points 4 months ago

This is what happens when you vibe-code your OS.

save

path: 0 24471670, hotness: undefined, score: 58, children: 2

lord_ryvan 1 point 4 months ago

It has been like this since long before coding LLMs.

save

path: 0 24471670 24485094, hotness: undefined, score: 1, children: 1

Tlaloc_Temporal 3 points 4 months ago

It got much worse when they went AI First.

Can they just get to the extinguish step already?

save

path: 0 24471670 24485094 24515169, hotness: undefined, score: 3, children: 0

Pika 43 points 4 months ago

How do you break the recycle bin... all it is is a pseudo folder that is present across all drives. All it does it recurse every drive and look for the path driveletter:\$RECYCLE.BIN\Account_SID

save

path: 0 24472499, hotness: undefined, score: 43, children: 5

AbsolutelyClawless 33 points 4 months ago

Microsoft acknowledged a bug in the June 2026 update that displays internal file names instead of real names in Recycle Bin confirmation dialogs.

save

path: 0 24472499 24474148, hotness: undefined, score: 33, children: 4

Romkslrqusz 24 points 4 months ago

Yup, totally broken then. Unusable.

Gotta love headline hyperbole lol

save

path: 0 24472499 24474148 24474711, hotness: undefined, score: 24, children: 2

Buddahriffic 4 points 4 months ago

There's different levels of broken. Like a drawer that doesn't close all the way still works as a drawer, and while I would call a drawer with its bottom busted out more broken than one that just won't close, both could use some repairs.

save

path: 0 24472499 24474148 24474711 24488111, hotness: undefined, score: 4, children: 0

Ghoelian 3 points 4 months ago

No one said it was unusable. This does sound objectively broken though.

save

path: 0 24472499 24474148 24474711 24488441, hotness: undefined, score: 3, children: 0

Pika 2 points 4 months ago

I'm not familiar with microsoft enough to really know what an internal file name entailed but, looking it up on other sources, it appears it made it so the files that appeared on the delete prompts were named to things like $Rxxxxx.ext which I'm not sure how could even happen. but yea the actual files in the can were named correctly, and they were deleted (or restored) as well. so its definitely a more minor bug.

save

path: 0 24472499 24474148 24489944, hotness: undefined, score: 2, children: 0

lorty 32 points 4 months ago

How do you break the trash bin...

save

path: 0 24472247, hotness: undefined, score: 32, children: 2

gibson 20 points 4 months ago

They didnt, this was basically fake news. They broke a string in a dialog that shows in certain cases.

I hate windows and Microsoft a lot BTW.

save

path: 0 24472247 24474710, hotness: undefined, score: 20, children: 0

Ooops 16 points 4 months ago

Coding in uncommented brainfuck... or -more realistic nowadays- vibe coding.

save

path: 0 24472247 24472750, hotness: undefined, score: 16, children: 0

muhyb 23 points 4 months ago

At one point, they'll be so deep in vibe code no human would be able to rescue Windows. And it doesn't seem too far.

save

path: 0 24474018, hotness: undefined, score: 23, children: 1

clucose 22 points 4 months ago

That happened already without vibe coding.

save

path: 0 24474018 24474532, hotness: undefined, score: 22, children: 0

MalReynolds 12 points 4 months ago

Ha-Ha

Somebody Else's Problem ;)

save

path: 0 24476505, hotness: undefined, score: 12, children: 0

sbv 9 points 4 months ago

Jesus

save

path: 0 24474613, hotness: undefined, score: 9, children: 0

SubArcticTundra 6 points 4 months ago

Finally Microsoft learns the art of the Bugfix

save

path: 0 24476608, hotness: undefined, score: 6, children: 0

Aneorthisio 5 points 4 months ago

Don't hold your breath, they took over a year to fix the disappearing cursor issue on some distributions of Win11 in 2024-2025, the cause was rooted in the interaction between the brand new desktop window manager and the legacy cursor rendering path that hadn't been updated since Vista, when moving the mouse between an application rendered with modern XAML components and a legacy system window, the cursor would sometimes become fully transparent, it was still there but invisible to the user until system reboot, turns out that building fluid fancy modern UI elements on top of a legacy Win32 framework does that sometimes.

save

path: 0 24489119, hotness: undefined, score: 5, children: 0

Ghoelian 5 points 4 months ago

What the hell is that website. They're just AI-aggregating news?

The website itself also looks pretty much exactly the same as default vibe-coded websites with no real style direction (which is to say default shadcn for the most part)

save

path: 0 24488505, hotness: undefined, score: 5, children: 0

MonkderVierte 3 points 4 months ago

Every week on Windows Microsoft.

save

path: 0 24485636, hotness: undefined, score: 3, children: 0

hoohoohoot 2 points 3 months ago

save

path: 0 24742363, hotness: undefined, score: 2, children: 0

raman_klogius 2 points 4 months ago

The patch has 3 spikes that punctures more holes

save