lennivelkant

Why do you piss in bleach?

If you have no idea how long it may take and if the issue will return - and particularly if upper management has no idea - swapping to alternate solutions may seem like a safer bet. Non-Tech people tend to treat computers with superstition, so "this software has produced an issue once" can quickly become "I don't trust anything using this - what if it happens again? We can't risk another outage!"

The tech fix may be easy, but the manglement issue can be harder. I probably don't need to tell you about the type of obstinate manager that's scared of things they don't understand and need a nice slideshow with simple words and pretty pictures to explain why this one-off issue is fixed now and probably won't happen again.

As for the question of scale: From a quick glance we currently have something on the order of 40k "active" Office installations, which mostly map to active devices. Our client management semi-recently finished rolling out a new, uniform client configuration standard across the organisation ("special" cases aside). If we'd had CrowdStrike, I'd conservatively estimate that to be at least 30k affected devices.

Thankfully, we don't, but I know some amounts of bullets were being sweated until it was confirmed to only be CrowdStrike. We're in Central Europe, so the window between the first issues and the confirmation was the prime "people starting work" time.

...and just how many PCs do you intend to "reboot into safemode delete one bad file and then reboot again"? Manually, or do you have some remote access tool that doesn't require a running system?

Having seen Excel used creatively, I think it's an exaggeration. It would make collaboration entirely impossible. I assume they have several smaller ones, with more or less - but not exactly - the same layout as it has been adapted for new use cases, and the only way to transfer records from one to the other is to manually copy and paste the info to the relevant cells, but mind the order you do it in and double check, or the Frankenstein's Macro running half the logic will crash.

I think it's time to expand the Clown-Empire and add ClownSocialServices.lol and ClownFlare to its Vassals.
What do we call the head of state? The Witish Clown?

Accessible through my corporate network. Fun thing, that.

...provided it runs on CrowdStrike-protected systems. I would expect the site's operator to make sure to avoid that if they can help it.

But what would it even change? The businesses would no longer be able to make an explicit agreement, probably have to pay a fine, but can they be forced to advertise or will they just proceed to coincidentally all decide not to advertise without explicitly colluding?

Why would you want backwards compatibility? To play games you already own and like instead of buying new ones? Now now, don't be ridiculous.

Sarcasm aside, I do wonder how technically challenging it is to keep your system backwards-compatible. I understand console games are written for specific hardware specs, but I'd assume newer hardware still understands the old instructions. It could be an OS question, but again, I'd assume they would develop the newer version on top of their old, so I don't know why it wouldn't support the old features anymore.

I don't want to cynically claim that it's only done for profit reasons, and I'm certainly out of my depth on the topic of developing an entire console system, so I want to assume there's something I just don't know about, but I'm curious what that might be.

27, I dimly remember what Winamp was (never used it though) and extrapolated what Skins would be. I assume they're essentially an archive of image files used to give a music player a custom look? Except they're not technically restricted to image files and can apparently contain other files too, which I assume will make them invalid as skins, i.e. corrupted.

How far off am I?

Mind, I'm far from representative for my age group, given my IT expertise.

I believe Robustness was the term I learned years ago: the ability of a system to gracefully handle user error, make it easy to recover from or fix, clearly communicate what was wrong etc.

Of course, nothing is ever perfect and humans are very creative at fucking up, and a lot of companies don't seem to take UX too seriously. Particularly when the devs get tunnel vision and forget about user error being a thing....

I used to sneer at the kids in my class that used it. Must have been fairly shortly after it launched, something like fourteen to fifteen years ago. I'm still grappling with a certain inertia when it comes to switching away from something I have relied on for so long, but I'm coming around to the idea of giving DDG a try at least (irrational as it is, I've been reluctant to even try - I suspect out of fear of liking it and having to change).

Past Me would be exasperated that Present Me is even toying with the idea. But then, Past Me had a lot of stupid takes anyway.