I’ve yet to convince anyone on this forum on this topic, but I’ll try one more time.
Take a step back, and let’s view this from our side, the software updater’s side and your side.
We release software, and it works in our testing. Everywhere, as far as we can tell, and we even write a program to check that to tell people ahead of time if it’s not going to work for them.
Then, something changes on the end user’s computer. They’re upset, because they feel they haven’t done anything. In reality, what they’ve done is to allow updates to their computer. Every software company involved in these updates tries to do this because they know how many technical noobs there are out there, and how many hackers and hack attempts there are, and they’re trying to help protect themselves and their users. That’s not a bad thing.
But when you want to control how software renders, displays things, or even works in general, updates are dangerous without extensive testing. Most updates have no affect on security, but are lumped in to the mix, believing to be a good thing.
So there’s an incongruence. I look at it as: all sides have their merits. But were I an end user and not on my side of the fence, I’d take action. For example, I haven’t updated 3 popular apps on my iPhone and never will because of bloat (for greater lack of privacy on my part’s sake) and the fact that everything they do can be done in a browser (not always as easily, but possible). This also allows updates to happen much quicker - the app has to be built, tested, and notably run through Apple’s approval process. Web does not. If you told me your issue was a bug in SketchUp, and it was on the web, we could turn around and fix that in reasonable time. SketchUp is a big client product, that takes a lot of infrastructure to turn around and fix, every time Microsoft or Apple or any video card company changes something.
But we do that in certain situations. Just today, we released the 3rd maintenance release of SketchUp 2017, because Apple is due to release High Sierra, according to the rumors on the internets, on September 25, and LayOut had issues on High Sierra. So it’s not out of the question.
From my viewpoint, you’re not only asking us to fix software from OS releases, but we should do something after Intel releases driver updates. Or NVIDIA. Or AMD. Or Apple. Or Microsoft. Or your anti-virus software. That becomes a bit tenuous but it could be done, because after all it’s SOFTware: crazy things are possible. And if the breaks are serious without a workaround, that would certainly be a good reason to tackle the issue. But there are multiple workarounds for this: don’t let Intel update your driver, or don’t automatically take updates from Microsoft. Inspect them, search the internet for reactions to them. As an ex-Apple guy, me and my ex-FruitCo buddies HATE how Apple now constantly nags you about minor updates. But we know why they do it. When I started working on SketchUp, @Last Software was on a “do not break” list for an OS, and even if it was our fault, the OS company would make it work and tell us about it. Ah, for the good old days of those fixes, and custom OS kernel patches by request before that in the 90’s.
You can dislike me or SketchUp for not addressing instantly someone else’s changes that affect us, but I hope you’ll at least have the knowledge to get that it’s not a simple black and white issue.
I wrote a whole bunch of extra thoughts in this thread, as I’ll link here and likely not respond in the future, unless there’s some extraordinary event that demands it.