top | item 21065114

(no title)

theclaw | 6 years ago

It now looks as though it might be Google Chrome. Whoooops.

https://mrmacintosh.com/google-chrome-keystone-is-modifying-...

e: hn discussion here: https://news.ycombinator.com/item?id=21064663

discuss

I can't wait for the post mortem, I wasn't expecting anything with Avid/PACE but if it's Google's problem then maybe we'll get info.

I work in this space (and am a casual user in the space) and I really want to know why /private/var was getting unlinked through a normal update and why Avid got pinged for it.

ratww|6 years ago

> why Avid got pinged for it

I think that was just because it was Avid users discovered it on the FB group[1].

I thought it was cool of their CEO to talk to the community, despite no evidence of it being their fault.

[1] https://www.facebook.com/groups/mediacomposer/permalink/1015...