News for hackers. Stuff that matters.
Re:Fuchsia is not Linux by dingo_bat on Wednesday April 11, 2018 @08:49PM (#16817141)
Is there an example of an os which doesn't have blocking io? To me it seems that blocking io will be needed at some level. You can of course put wrappers around it and present it as async. But in many applications you want to go as low as possible, and in my imagination blocking calls will be the lowest.
Re:Fuchsia is not Linux by zzzcpan on Wednesday April 11, 2018 @09:36PM (#16817338)
It's the other way around. Low level is all async everywhere, blocking is sort of just telling the kernel to wait for async op to complete before running the process.
Re:Fuchsia is not Linux by rurban on Thursday April 12, 2018 @10:54AM (#16821539)
Midora, Singularity in an OS. Pony in a language.

The goal is to avoid blocking, not to offer async also. That's a lost cause.

Fuchsia once had the goal to offer async only, but then some manager decided that he needs some blocking, and then it was gone.

non-blocking only is lower level than blocking. You can always wait indefinitely for that callback, but usually you have a default timeout. L4 for example offers that API.