Hacker News new | past | comments | ask | show | jobs | submit login

I have never needed to reboot because of permissions, basically just had to click “allow” a few times, so this stuff doesn’t really bother me. It’s a very slight inconvenience.

Big Sur performance on older hardware has been a disaster though. Even on a $2500 MBP 15” from 2017. On M1 though it’s excellent.

Every update I need two reboot twice to get the google drive system extension to load, but that’s the only issue I’ve had like that.

However big sur runs alright on my 2015 MacBook!

Having written system extensions (both kext and DriverKit), that seems more like an issue with the extension itself.

That may, but Apple broke a formerly working API. If Google can't figure it out, that's a signal.

I mean... no?

If you're referring to the Kext/DriverKit changeover, this is just false - Kexts still work in Big Sur, they're just trying to slowly shift the ecosystem to DriverKit. Nothing has truly changed there yet.

If you're referring to a broken thing within Kexts/IOKit itself, that would be a pretty severe bug that would get attention within Apple. I feel confident saying this as I've reported bugs like this and they get appropriate priority levels.

Lastly, if you're writing (signed) driver code, you generally have access to resources within Apple to get answers to questions. I'm not even a large company and it was relatively easy to get in touch with those teams - and this stands in contrast to other teams within Apple.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact