First Rule of Google Fuchsia OS Is to Not to Talk About It
fuchsiatalks.com
First Rule of Google Fuchsia OS Is to Not to Talk About It
1–10 of 58 posts
Re: First Rule of Google Fuchsia OS Is to Not to Talk About It
#2Not really any new information here. It's fun to speculate about what Fuchsia might become, but it's pretty clear Google's not ready to announce anything yet. The only reason we even know it exists is because they made the source code public.
Re: First Rule of Google Fuchsia OS Is to Not to Talk About It
#3Saw this rant about Fuchsia on reddit that appears on the surface to make some good points: https://www.reddit.com/r/programming/comments/6a026o/googles... Not my area of expertise for sure though.
Any kernel dev types here had a chance to look at Fuchsia? Is the criticism warranted?
Update: Fixed link to point at the right comment.
Edit: Should have mentioned the tone is a bit over the top. More interested in the actual points raised though.
Re: First Rule of Google Fuchsia OS Is to Not to Talk About It
#4Since site is down:
https://webcache.googleusercontent.com/search?q=cache:Ej2flu...
Re: First Rule of Google Fuchsia OS Is to Not to Talk About It
#5Saw this rant about Fuchsia on reddit that appears on the surface to make some good points: https://www.reddit.com/r/programming/comments/6a026o/googles... Not my area of expertise for sure though. Any kernel dev types here had a chance to look at Fuchsia? Is the criticism warranted? Update: Fixed link to point at the right comment. Edit: Should have mentioned the tone is a bit over the top. More interested in the ac…
I don't see the rant; that's just the link to the whole discussion. Did you mean to link to a particular comment?
I haven't followed Fuchsia that closely, but I was under the impression that the team consisted of some all-star kernel developers; former BeOS people for example?
Re: First Rule of Google Fuchsia OS Is to Not to Talk About It
#6Saw this rant about Fuchsia on reddit that appears on the surface to make some good points: https://www.reddit.com/r/programming/comments/6a026o/googles... Not my area of expertise for sure though. Any kernel dev types here had a chance to look at Fuchsia? Is the criticism warranted? Update: Fixed link to point at the right comment. Edit: Should have mentioned the tone is a bit over the top. More interested in the ac…
Can't tell which comment you mean, but if you mean the criticism that Dart is used as a userspace language, that's not related to the choice of kernel (which seems fine to me).
Re: First Rule of Google Fuchsia OS Is to Not to Talk About It
#7Saw this rant about Fuchsia on reddit that appears on the surface to make some good points: https://www.reddit.com/r/programming/comments/6a026o/googles... Not my area of expertise for sure though. Any kernel dev types here had a chance to look at Fuchsia? Is the criticism warranted? Update: Fixed link to point at the right comment. Edit: Should have mentioned the tone is a bit over the top. More interested in the ac…
Did you intend to link to this?
https://www.reddit.com/r/programming/comments/6a026o/googles...
Re: First Rule of Google Fuchsia OS Is to Not to Talk About It
#8Saw this rant about Fuchsia on reddit that appears on the surface to make some good points: https://www.reddit.com/r/programming/comments/6a026o/googles... Not my area of expertise for sure though. Any kernel dev types here had a chance to look at Fuchsia? Is the criticism warranted? Update: Fixed link to point at the right comment. Edit: Should have mentioned the tone is a bit over the top. More interested in the ac…
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/conce... https://fuchsia.googlesource.com/magenta/+/master/docs/sysca...
(It's all a work in progress, which has been and will continue to evolve)
Re: First Rule of Google Fuchsia OS Is to Not to Talk About It
#9Saw this rant about Fuchsia on reddit that appears on the surface to make some good points: https://www.reddit.com/r/programming/comments/6a026o/googles... Not my area of expertise for sure though. Any kernel dev types here had a chance to look at Fuchsia? Is the criticism warranted? Update: Fixed link to point at the right comment. Edit: Should have mentioned the tone is a bit over the top. More interested in the ac…
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.…
(For context, swetland is currently the main contributer to Magenta, Fuchsia's kernel: https://github.com/fuchsia-mirror/magenta/graphs/contributor...)
Re: First Rule of Google Fuchsia OS Is to Not to Talk About It
#10Saw this rant about Fuchsia on reddit that appears on the surface to make some good points: https://www.reddit.com/r/programming/comments/6a026o/googles... Not my area of expertise for sure though. Any kernel dev types here had a chance to look at Fuchsia? Is the criticism warranted? Update: Fixed link to point at the right comment. Edit: Should have mentioned the tone is a bit over the top. More interested in the ac…
Did you intend to link to this? https://www.reddit.com/r/programming/comments/6a026o/googles...
Yes...updating. thanks.