On: No, it wasn’t a virus; it was Chrome that stopped ...

[tannhaeuser]

That's hardly an excuse, is it? The question is whether, after this incident, you're still comfortable with using any Google app.

[cloudwalking → tannhaeuser]

How many Chrome updates have you gotten that did not break your computer? Was your computer broken by this? My understanding is the rollout was stopped fairly quickly.

[hinkley → cloudwalking]

How many times did Ann Rule interact with Ted Bundy and he didn't murder her once?

I mean, he can't be all that murdery, right?

We're talking about nuking a filesystem, not glitching out randomnly. That it hasn't nuked the filesystem before is not extenuating circumstances. It doesn't speak to character either.

[filleduchaos → hinkley]

Yes, an app accidentally deleting a folder after you've turned off protections on that folder is definitely the same thing as serial killing.

People here sometimes.

[hinkley → filleduchaos]

> That's hardly an excuse, is it?

[filleduchaos → hinkley]

I was commenting on the hilariously bad choice of analogy.

[zepto → cloudwalking]

How many other equally dangerous and irresponsible mechanisms are Google using?

[dreamcompiler → tannhaeuser]

I'm as comfortable using Google apps today as I was a week ago, because I figured out long ago how to disable Keystone permanently. (It wasn't easy.)

But I am rather pissed at Apple because SIP is a global switch and with it enabled, there are several significant, legitimate things you cannot do with your own computer. SIP should work like sudo, not like a meta version of root. If it did so, nobody would have been affected by this week's Google nonsense.

[MarkyC4 → dreamcompiler]

> with it enabled, there are several significant, legitimate things you cannot do with your own computer.

For those wondering about such a use case: the only way to get eGPU's working on <=2015 MBPs is to disable SIP (and use purge-wrangler). It's not officially supported because 2015s don't have TB3