Live data from Hacker News

Google’s Fuchsia OS on the Pixelbook

arstechnica.com

81–90 of 126 posts

Re: Google’s Fuchsia OS on the Pixelbook

#81

Earlier quoted context omitted.

How exactly is Google getting power here? The code is totally open. They just seem to be giving themselves more flexibility and potential to build better products. If anything, this will result in less power over the Linux kernel for Google. It seems like that’s something you’d appreciate. (My response to s2g’s reply below because HN is terrible for commenting: I see your point that they now unilaterally control how…

Fuschia uses a BSD style license whereas the Linux kernel is GPL. Google or hardware vendors can modify the Fuschia code without sharing the changes with the public, for better or worse.

Google, as the copyright owner, could do that, or let hardware vendors do so, even if it was GPL.

BSD-style means that anyone can do that, even Google's competitors, without any additional permission from Google.

Re: Google’s Fuchsia OS on the Pixelbook

#82
post #70

Earlier quoted context omitted.

How exactly is Google getting power here? The code is totally open. They just seem to be giving themselves more flexibility and potential to build better products. If anything, this will result in less power over the Linux kernel for Google. It seems like that’s something you’d appreciate. (My response to s2g’s reply below because HN is terrible for commenting: I see your point that they now unilaterally control how…

Everyone said the same thing about Android.

...and Amazon went ahead and forked it, in addition to CyanogenMod, Paranoid, Copperhead, "HALFB4kedMod 0.9Beta2(No camera)"[1] and so on. Android's openness is not just empty words.

1. Until the developer changes phones and loses interest. Nevertheless, thank goodness for XDA.

Re: Google’s Fuchsia OS on the Pixelbook

#83

Earlier quoted context omitted.

you're right. it should be written in typescript. or maybe the java prerelease from 1995.

Urg... https://externos.io/ Edit: > eXperience the future. I don't know what gets me more, the idea of a js os, the bad capitalization, the period at the end of a non sentence, the cliché expression...

Whoever's behind it seems to be stuck at the "gaussian blur compensates for all forms of design inexperience!!1" stage too.

Re: Google’s Fuchsia OS on the Pixelbook

#84

Earlier quoted context omitted.

How exactly is Google getting power here? The code is totally open. They just seem to be giving themselves more flexibility and potential to build better products. If anything, this will result in less power over the Linux kernel for Google. It seems like that’s something you’d appreciate. (My response to s2g’s reply below because HN is terrible for commenting: I see your point that they now unilaterally control how…

> My response to s2g’s reply below because HN is terrible for commenting: Click on the comment’s link (the “x hours ago”) to reply.

It wasn’t that. It was rate limiting me... for some reason.

Re: Google’s Fuchsia OS on the Pixelbook

#85
post #70

Earlier quoted context omitted.

Everyone said the same thing about Android.

...and Amazon went ahead and forked it, in addition to CyanogenMod, Paranoid, Copperhead, "HALFB4kedMod 0.9Beta2(No camera)"[1] and so on. Android's openness is not just empty words. 1. Until the developer changes phones and loses interest. Nevertheless, thank goodness for XDA.

And by now not even the caller app, or the phonebook app, or the calendar, or Homescreen, or settings, or search are open anymore.[1]

Everything now requires Google's proprietary services

Oh, and Google prevents OEMs from cooperating with Amazon.[2]

As result, Android is almost completely controlled by Google.

And you call that "open"?

    ________________________
[1] To disprove this, please find me the full current source code of the Google Dialer, Google Contacts, Android Nessages, Google Calendar, Pixel Launcher, and Google Search apps — all these used to be open source in Android 2.3.7, if you find me the full source code of their current versions, I'll take this point back.

[2] See the ongoing Antitrust case in the EU against Google

Re: Google’s Fuchsia OS on the Pixelbook

#86
post #44

Earlier quoted context omitted.

Depending on the future direction they take this, it might end up replacing OpenBSD for me. Mac OS X and OpenBSD are my daily drivers, but at their core, they are BSDs, and less and less I find myself using the NeXTSTEP portion of Mac OS X and more and more time in BSD-land, which is leading me to move more and more of my overall computer time to OpenBSD which is a great operating system but is still largely a contin…

Don’t hold your breath. The zircon API isn’t innovative in any modern sense. Additionally it’s bloated and not clean like L4. It’s just in house IP for Google. (HN won’t let me directly reply to the comment below so here it is: Nothing in zircon doesn’t already exist on Linux or any other modern kernel. Additionally it has bloat, like 3 distinct IPC mechanisms. Even further, if it ends up being any technical person’s…

You think the lack of technical innovation is what makes products fail? Seems to me that it's actually the opposite that's true.

Re: Google’s Fuchsia OS on the Pixelbook

#87
post #24

There's no point to these early Fuschia review attempts. I don't see how it demonstrates anything. It's like looking at the famous first email from Linus Torvald and figuring out what the os would be in the end. So it boots, it has windows, but not apps, and prints some things to the screen. It tells us nothing about real intentions, future capabilities, etc.

As somebody who read that famous first email and shared it around her lab: We were all tremendously excited, and spent days discussing it. This is the same thing - it's exciting . It's trying to do things many of us have thought of, but never worked on. It's new technology. It's something that, in our hearts, we want to succeed just because the alternatives are all grungy and dusty and carry the compatibility fixes o…

It's all written in C++, so from a security and reliability perspective, I'm sketical it's going to offer much improvement over Linux. I don't see any evidence yet of "new technology". I'm happy to be proven wrong.

Re: Google’s Fuchsia OS on the Pixelbook

#88
post #87
post #24

Earlier quoted context omitted.

As somebody who read that famous first email and shared it around her lab: We were all tremendously excited, and spent days discussing it. This is the same thing - it's exciting . It's trying to do things many of us have thought of, but never worked on. It's new technology. It's something that, in our hearts, we want to succeed just because the alternatives are all grungy and dusty and carry the compatibility fixes o…

It's all written in C++, so from a security and reliability perspective, I'm sketical it's going to offer much improvement over Linux. I don't see any evidence yet of "new technology". I'm happy to be proven wrong.

> It's all written in C++, so from a security and reliability perspective, I'm sketical it's going to offer much improvement over Linux.

Are you an expert in C? or in C++?

Re: Google’s Fuchsia OS on the Pixelbook

#89
post #87
post #24

Earlier quoted context omitted.

As somebody who read that famous first email and shared it around her lab: We were all tremendously excited, and spent days discussing it. This is the same thing - it's exciting . It's trying to do things many of us have thought of, but never worked on. It's new technology. It's something that, in our hearts, we want to succeed just because the alternatives are all grungy and dusty and carry the compatibility fixes o…

It's all written in C++, so from a security and reliability perspective, I'm sketical it's going to offer much improvement over Linux. I don't see any evidence yet of "new technology". I'm happy to be proven wrong.

I can use your logic to prove that there is no evidence of new technology in the Falcon 9 rocket.

After all, it is developed with very similar tools compared to every other rocket in existence.

Re: Google’s Fuchsia OS on the Pixelbook

#90
post #85

Earlier quoted context omitted.

...and Amazon went ahead and forked it, in addition to CyanogenMod, Paranoid, Copperhead, "HALFB4kedMod 0.9Beta2(No camera)"[1] and so on. Android's openness is not just empty words. 1. Until the developer changes phones and loses interest. Nevertheless, thank goodness for XDA.

And by now not even the caller app, or the phonebook app, or the calendar, or Homescreen, or settings, or search are open anymore.[1] Everything now requires Google's proprietary services Oh, and Google prevents OEMs from cooperating with Amazon.[2] As result, Android is almost completely controlled by Google. And you call that "open"? ________________________ [1] To disprove this, please find me the full current sou…

You can still go fully open; https://microg.org/ and https://f-droid.org/en/ I don't have Pay, and no cloud push notifications, and the GPS assist isn't quite as perfect, but the only real bugbare is no swyping keyboard.
Post reply on HN