johanj
Joined 11 years ago
Joined 11 years ago
Essentially, they avoided CFS quota throttling by assigning exclusive CPU cores via cpusets. That sacrifices some burstability and packing efficiency in exchange for stronger, more predictable CPU isolation.
> Contract terms were roughly as follows:
> * Uber reports issues to github.com/ziglang/zig and pings Loris.
> * Loris assigns it to someone in ZSF.
> * Hack hack hack hack hack.
> * When done, Loris enters the number of hours worked on the issue.
>
> Uber has a right to ZSF members’ time. We have no decision or voting power whatsoever with regards to Zig. We have right to offer suggestions, but they have been and will be treated just like from any other third-party bystander. We did not ask for special rights, it’s explicit in the contract, and we don’t want that.[1]: https://blog.archive.org/2017/04/17/robots-txt-meant-for-sea...
It is pretty common for spouses to have a finger added on their spouse’s phone for unlocking it with Touch ID, e.g., when you’re driving and get a message, you can give it to your spouse who can reply.
Many parents also have a finger added on their young children’s phones.
None if these scenarios are really possible with Face ID, because you’ll end up training Face ID with two faces. And while phones are usually used by only a single person, it is not an uncommon scenario to have a secondary user.