What a monster... and apparently in more ways than one!
Perhaps there should be an "emergency beheading axe" available for these extreme outliers, or a third (fourth, fifth...?) dose.
91,272 karma · joined December 8, 2013
What a monster... and apparently in more ways than one!
Perhaps there should be an "emergency beheading axe" available for these extreme outliers, or a third (fourth, fifth...?) dose.
Richard Stallman's Right to Read (1997) made a similar observation.
...and despite MS having their own AI, one which many here have said their employees are required to use, and yet bugs like this remain unfixed, is a good example of why AI isn't replacing any developers. Ultimately a human has to care enough to even point the AI at the problem.
With AI, instead you feel a connection to the sum of all humanity.
The bug first appeared with the monthly updates 2023-03 (KB5023706) for Windows 11 and 2023-04 (KB5025221) for Windows 10. The initial releases of Windows 10 and Windows 11 22H2 with no updates do not have this bug
...and everything older likely doesn't either, especially from the time when VCDs were far more commonly used.
Pulling the files off (and ignoring errors, the way Windows does) loses that.
I suspect this might be the clue; perhaps some overzealous "security scan" tool (or these days, AI) flagged a "bug" in the error handling path, and something was done to appease it, but created this other subtle bug.
Put a hot air gun on the back of the board, and they'll either just drop out or do so with a small poke of the pins.
Everything is a derivative work.
It's great to see the delusion of Imaginary Property vanishing.
JS is a huge attack surface. It's better if it isn't used where it isn't actually needed.
Double hell no. The majority of the time it's a log file with lots of repetitive lines, and I'm definitely NOT going to remember exactly the line, especially after the disruption of accidentally jumping somewhere unexpected.
...like it was back in the days when Windows actually had a very customisable UI[1], and then the "skinnable" UIs of the early 2000s (most of which were extremely gaudy, but then again, maybe that was what the majority of the population wanted.) Now it has devolved into little more than this: https://support.microsoft.com/en-us/windows/experience/perso...
[1] and one of the included color schemes was indeed crazy, but a good demonstration of what was available: https://news.ycombinator.com/item?id=46247605
...and even if the app is a game, it can still make great use of Win32 controls creatively. Minesweeper is one example that comes with Windows, and I remember plenty of other casual (non-3d) games in the 90s/early 2000s making use of buttons, both ownerdrawn and stock, likely to avoid having to write their own hit-testing code.
Pure Win32 still works, and is the most efficient and consistent.
The frameworks that actually wrap a Win32 scrollbar are the ones doing it right; the ones that (badly) reinvent a scrollbar are the ones to avoid. The real problem in this case isn't frameworks, but how they make use of the platform capabilities.
(Incidentally this is also one of my gripes with the Intel Macs, wanting to put Linux on one but having zero configurability pre-OS is a huge pain. Meanwhile a standard PC BIOS with the equivalent hardware has plenty of options. Maybe I'll get around to (vibe)porting a regular BIOS to mine...)
Genetic variation probably has a bigger role than we'd like to admit. There are definitely outliers. I know smokers who lived into their 90s, and non-smokers who died much younger. The sibling comment says they lived into their 70s, which is probably average.
...and then there's https://en.wikipedia.org/wiki/Jeanne_Calment#Health_and_life...
Calment continued smoking in her elderly years until she was 117