3 ms·

I'd suggest that it's possible we're using simple, but functional placeholder implementations of things so the entire system can boot and run, and then various

I'd suggest that it's possible we're using simple, but functional placeholder implementations of things so the entire system can boot and run, and then various parts of it can be worked on at various paces, in parallel, etc. Lot of moving parts in a kernel, or OS, and one could try to write all of them in their final form first and hope they all work together when done, or one could take a more incremental approach. Personally, I think the evolution of the general kernel design / syscall interface, love it or hate it, is more interesting than have we optimized the timer implementation yet... https://fuchsia.googlesource.com/magenta/+/master/docs/concepts.md https://fuchsia.googlesource.com/magenta/+/master/docs/conce... https://fuchsia.googlesource.com/magenta/+/master/docs/syscalls.md https://fuchsia.googlesource.com/magenta/+/master/docs/sysca... (It's all a work in progress, which has been and will continue to evolve)

Ajedi32 9y ago
(For context, swetland is currently the main contributer to Magenta, Fuchsia's kernel: https://github.com/fuchsia-mirror/magenta/graphs/contributors https://github.com/fuchsia-mirror/magenta/graphs/contributor...)
- swetland 9y ago
  The stats are a little unfair there, as I've done a lot of rearranging and housecleaning, which tends to inflate github's scoreboards. I suspect more of my work is outside the kernel than in (driver model/hosting/managing, userspace core glue, etc), but certainly I'm to blame for a reasonable chunk of kernel code too.
mckillop 9y ago
I also encourage anyone that sees something that could be done better to sign up and submit some code!
- tyingq 9y ago
  I suspect some are holding back since there's not been much shared about the end purpose. At the moment there's still speculation as to whether it's for mobile devices, desktops, both, or something else.
- kuschku 9y ago
  That would be a lot easier if it were GPL with no CLA. The way it currently is, it looks like something Google will develop with the help of the FLOSS community, and then take the code, close it, and continue everything else in the dark. As they’ve done with most parts of Android by now.

Ajedi32 9y ago

(For context, swetland is currently the main contributer to Magenta, Fuchsia's kernel: https://github.com/fuchsia-mirror/magenta/graphs/contributors https://github.com/fuchsia-mirror/magenta/graphs/contributor...)

swetland 9y ago
The stats are a little unfair there, as I've done a lot of rearranging and housecleaning, which tends to inflate github's scoreboards. I suspect more of my work is outside the kernel than in (driver model/hosting/managing, userspace core glue, etc), but certainly I'm to blame for a reasonable chunk of kernel code too.

mckillop 9y ago

I also encourage anyone that sees something that could be done better to sign up and submit some code!

tyingq 9y ago
I suspect some are holding back since there's not been much shared about the end purpose. At the moment there's still speculation as to whether it's for mobile devices, desktops, both, or something else.
kuschku 9y ago
That would be a lot easier if it were GPL with no CLA. The way it currently is, it looks like something Google will develop with the help of the FLOSS community, and then take the code, close it, and continue everything else in the dark. As they’ve done with most parts of Android by now.