the part that is challenging to me is why anyone expects that to actually work?
have you been paying attention for the last 20+ years now?
i want to say there was maybe a period of 5 years around mid 2000 where it did but microslop has been awful for decades
and i can count on 2 hands the number of times the issue was urgent enough to need an immediate response regardless of what middle management thinks (and phone calls worked fine)
so over working for bigcap company cultures and middle managers having too little actual work
ms literally pushed a vibe coded update that boot lopped multiple dev machines for a week before we resolved it
technically it was fixed same day but only because we have regular nightly images and other machines
that alone should be enough of a reason, this is just more shit on the camel’s back
but so you know I’m not downvoting you, nothing you’ve said is unreasonable, I just really have no patience with current tech companies and clearly lemmy is sick of ms’ shit
Microsoft pushing a bad update and breaking dev machines is an issue with your it department. Every single OS pushes bad updates thats why you stagger your releases through rings so you can catch the issues early and minimise downtime.
Imagine if we stopped using linux because of a bad update.
You just said you recovered the windows boot loop.
Linux breaks booting all the time. Its so common its every linux user knows how to fix it. Pick the distro and you’ll find tons of boot issues after major updates.
yea recovered by reinstalling an image from before the update, the system was a complete brick otherwise
it took microslop 3 weeks to fix their shit, google it if you are confused, it wasn’t a limited hardware exposure issue, it was bad code
we’ve been running rhel stable for decades with never a single example like this, i’m not talking about one off hiccups, i’m talking about the entire main line being busted
pulling an example of loops from some random linux unstable distro or beta is meaningless
to claim otherwise is bullshit, again this is not normal, even ms hasn’t been this bad since early vista
the part that is challenging to me is why anyone expects that to actually work?
have you been paying attention for the last 20+ years now?
i want to say there was maybe a period of 5 years around mid 2000 where it did but microslop has been awful for decades
and i can count on 2 hands the number of times the issue was urgent enough to need an immediate response regardless of what middle management thinks (and phone calls worked fine)
so over working for bigcap company cultures and middle managers having too little actual work
By that logic dont bother implementing anything because what if it doesnt work.
It’ll work good enough for most and better than the current status situation.
or you know stop using overpriced miroshit products
pay your workers well and treat them like adults
and cut useless middle management
sadly my company still uses ms but at least they nail the other two
deleted by creator
You hate MS, I do as well but its not relevant to talk about throwing it all out. This is just about a minor feature release and lemmys overreaction.
ms literally pushed a vibe coded update that boot lopped multiple dev machines for a week before we resolved it
technically it was fixed same day but only because we have regular nightly images and other machines
that alone should be enough of a reason, this is just more shit on the camel’s back
but so you know I’m not downvoting you, nothing you’ve said is unreasonable, I just really have no patience with current tech companies and clearly lemmy is sick of ms’ shit
Microsoft pushing a bad update and breaking dev machines is an issue with your it department. Every single OS pushes bad updates thats why you stagger your releases through rings so you can catch the issues early and minimise downtime.
Imagine if we stopped using linux because of a bad update.
don’t act like this is normal
i can’t think of a linux release in the 22+ years that’s had a non recoverable boot loop
and who says it wasn’t staggered? doesn’t do a damn thing for those in the release group
You just said you recovered the windows boot loop.
Linux breaks booting all the time. Its so common its every linux user knows how to fix it. Pick the distro and you’ll find tons of boot issues after major updates.
yea recovered by reinstalling an image from before the update, the system was a complete brick otherwise
it took microslop 3 weeks to fix their shit, google it if you are confused, it wasn’t a limited hardware exposure issue, it was bad code
we’ve been running rhel stable for decades with never a single example like this, i’m not talking about one off hiccups, i’m talking about the entire main line being busted
pulling an example of loops from some random linux unstable distro or beta is meaningless
to claim otherwise is bullshit, again this is not normal, even ms hasn’t been this bad since early vista