3 ms·
>That’s not what this. This is largely about mitigating the damage that can be done once someone finds a memory safety error. Hmm, seems like Apple should do b
by panny 4y ago
>That’s not what this. This is largely about mitigating the damage that can be done once someone finds a memory safety error.
Hmm, seems like Apple should do better when there are perfectly good languages available which could prevent memory safety issues altogether. Seems like Apple would want to compete with Linux rather than watch it race away into the memory safe future, leaving XNU behind with legacy memory safety problems.
- olliej 4y agoOk, so rather than writing a comment where you shit on the people who work at Apple and actually do care about security, I suggest you actually read the article. Because the article lists those safe languages, and states why the existence of those safe languages does not solve security.
- pjmlp 4y agoWhy do you think they have Swift, have reduced their involvment into clang and are moving all kernel extensions into userspace?