@Gte @shac I hope lessons were learned and recorded.

Nothing like working on an os and then none of the experience being passed down.

@colinburgess @Gte Well, the joke was that Fuchsia was a retirement home for frustrated Android engineers. They were doing the opposite of Android in every way to fix all the fundamental problems with the first OS. What they ended up with was essentially a meta-OS that could theoretically do anything but in practice did nothing.

The kernel (zircon) is pretty good though and has some good ideas.

@shac @colinburgess @Gte I feel like the move is usually to speed run to BSD compatibility. Is that not the case with Fuchsia? I can’t imagine writing everything in user space from scratch
@unsaturated @shac @Gte yeah I would agree that portability of existing posix/unix based software is the death knell for the blue sky dreamers’ revolutionary OS’s
@unsaturated @colinburgess @Gte The goal was to make something secure by default. POSIX is incompatible with the fuchsia security model (and syscall model), so yes, rewrite all of userland.
Several years later, they are now maintaining a unix compatibility runtime as a key component.
@shac @colinburgess @Gte right at some point reality has got to set in once you realize that like Bash and Python and Ruby and awk and grep and find and etc are super useful.
@unsaturated @shac @colinburgess @Gte or these days, speedrun to hosting a Linux container
@joe @shac @colinburgess @Gte
tired: POSIX compliant
wired: Docker compliant