Live data from Hacker News

A Kernel Hacker Meets Fuchsia OS

a13xp0p0v.github.io

171–180 of 296 posts

Re: A Kernel Hacker Meets Fuchsia OS

#171
post #2

Very nice right up on how unfinished and insecure Fuchsia is as a result of it being so unfinished.

Unfinished might be a good excuse if it weren't running on Nest devices.

Nest devices don't run untrusted code. If you get code running on a Nest display, please let me know how, because I'd love to hack around on mine.

Re: A Kernel Hacker Meets Fuchsia OS

#172
post #170

Earlier quoted context omitted.

> I am not sure why there's so much negativity around Fuchsia. Easy: this is not the future we want. We don’t trust google. We don’t want an OS designed to further their goal of total control and surveillance capitalism.

It’s hilarious. I’ve been around long enough to remember people not trusting IBM and heralding Microsoft as the underdog with bright principles. Then it became Google being the white prince on a unicorn telling Micro$oft to eff off. For about a decade now we’re collectively in Not Trusting Google mode. “It’s all just a little bit of history repeatin’.”

But given that's open source shouldn't it be a bit better? If I don't agree with some parts of the OS I can fork the project and remove some stuff. Given that's open source you don't have to fully trust Google, you can check things yourself. I know I'm probably bring native, but I am hoping to see some changes in the space.

Re: A Kernel Hacker Meets Fuchsia OS

#173

Disclaimer: I made some contributions to Fuchsia and I am clearly biased. I am not sure why there's so much negativity around Fuchsia. From a technical point of view it's finally a serious attempt to do something new in the OS space. It might not be the right and perfect answer, but it might introduce new paradigms and maybe some fork of the project might be able to provide additional benefits for end users down the…

> I am not sure why there's so much negativity around Fuchsia. Easy: this is not the future we want. We don’t trust google. We don’t want an OS designed to further their goal of total control and surveillance capitalism.

> We don’t want an OS designed to further their goal of total control and surveillance capitalism.

What parts of the operating system design do this?

Re: A Kernel Hacker Meets Fuchsia OS

#174
post #59
post #16

Wow, it is surprising how awful every last bit of Zircon code reproduced here is. I have to guess the rest is about as bad. This dreck would never pass code review at my shop.

I skimmed through the article and nothing stood out. Can you give an example of a piece of code you didn't like?

Every last bit of Zircon code he reproduced in the article was a woolly mess that the code's author (not the article's) should be ashamed of. That the author found it easy to code an exploit for a system he knew so little about shows that the code is not just woolly, but actually bad.

Re: A Kernel Hacker Meets Fuchsia OS

#175

Earlier quoted context omitted.

Unlike Linux, Fuchsia is not under GPL. Another attempt at making Android less open.

>Unlike Linux, Fuchsia is not under GPL. It's under MIT (the kernel Zircon specifically since comparing with Linux). Whether a license allowing even more freedom is worse is arguable.

I know - it provides google the freedom to lock down the OS further and the freedom to implement proprietary drivers.

Yay for arguable freedom.

Re: A Kernel Hacker Meets Fuchsia OS

#176

Earlier quoted context omitted.

You want to limit what current and future generations of people can do with their computers because of something a computer illiterate grandma may have done in the 90s? No. Those people get newspapers and landlines.

You badly overestimate both the ability and interest of average people in learning to administrate their computers. They just want to get shit done and go do something else. Computers are a tool at best, and more often a super-annoying thing they have to deal with but hate every second of it. If they actually like any of the computers around them, it's probably the most locked-down ones: their phones and video game c…

You can have a locked down mode. You can even sell it turned on by default. But to exclusively prevent everyone from using their computers as they see fit because you think some people are too stupid to handle it? I don't believe you actually want that. I believe that's an excuse to ensure Apple gets a cut of everything that happens on their soon to be landfill machines.

If yes, man that's really dangerous thinking.

Re: A Kernel Hacker Meets Fuchsia OS

#177
post #47

The people who work on fuchsia are very good engineers - I’ve worked with many of them in person. But the project itself has always been a staff retention project. It only existed to keep said engineers from going to a competitor. I don’t know how any understanding of fuchsia is possible without this crucial fact

Does that mean you don't believe it's going to replace Android/AOSP? It's in some Nest devices right now.

Not sure if it's ever feasible to replace Android (it's going to take at least a decade even assuming that Google becomes serious) but I think ChromeOS seems a reasonable target. It's not going to be as spectacular as Android but a decently successful migration if done properly. At that moment, I guess people can make more serious investments into Fuchsia.

Re: A Kernel Hacker Meets Fuchsia OS

#178

Earlier quoted context omitted.

You can really tell who lived through the era of 20 stacked, all-unwanted browser "toolbars" and Bonzi Buddy and such, and who didn't. That didn't go away because people learned . And it never would have.

You want to limit what current and future generations of people can do with their computers because of something a computer illiterate grandma may have done in the 90s? No. Those people get newspapers and landlines.

[deleted]

Re: A Kernel Hacker Meets Fuchsia OS

#179

Earlier quoted context omitted.

You badly overestimate both the ability and interest of average people in learning to administrate their computers. They just want to get shit done and go do something else. Computers are a tool at best, and more often a super-annoying thing they have to deal with but hate every second of it. If they actually like any of the computers around them, it's probably the most locked-down ones: their phones and video game c…

You can have a locked down mode. You can even sell it turned on by default. But to exclusively prevent everyone from using their computers as they see fit because you think some people are too stupid to handle it? I don't believe you actually want that. I believe that's an excuse to ensure Apple gets a cut of everything that happens on their soon to be landfill machines. If yes, man that's really dangerous thinking.

I have almost zero interest in haxoring my phone, and just want it to always work and not let 3rd parties steal my info, automatically.

And I'm a life-long computer geek who's done professional mobile development. Most people care even less than I do. They just want it to work, because computers aren't their life, they just use them to get stuff done, or when someone else tells them they have to. Would it be sort of nice to have the option to unlock it? Yes, exclusively so I could run pirated games in emulators more easily, which is the only thing non-programmers I know with unlocked Android phones use all that freedom of theirs for. For most people, they'd not pay even a couple dollars to have the unlock option. It's worth basically nothing to them, because they do not have any actual use for it. But sure, it'd be nice. It's just not a big deal.

> If yes, man that's really dangerous thinking.

The NES had a DRM chip—a bad one, but still.

Some computers have been appliances, and some have been programmers' machines, for a long time, and the sky hasn't fallen. The former have just eaten some of the use cases for the latter, where a fully-capable general-purpose computer was at least as much of a liability as a boon.

Even Apple still makes normal-ass computers for people who need them. If your reaction to that statement is "pft, yeah, but they're clearly trying to get rid of those", well, people have been saying that for more than a decade, and it still hasn't happened and doesn't seem to be any closer, so... I'll believe it when I see it.

Re: A Kernel Hacker Meets Fuchsia OS

#180
post #170

Earlier quoted context omitted.

It’s hilarious. I’ve been around long enough to remember people not trusting IBM and heralding Microsoft as the underdog with bright principles. Then it became Google being the white prince on a unicorn telling Micro$oft to eff off. For about a decade now we’re collectively in Not Trusting Google mode. “It’s all just a little bit of history repeatin’.”

But given that's open source shouldn't it be a bit better? If I don't agree with some parts of the OS I can fork the project and remove some stuff. Given that's open source you don't have to fully trust Google, you can check things yourself. I know I'm probably bring native, but I am hoping to see some changes in the space.

MIT means it's only open source for as long as Google feels like it should be (and only the parts they want to keep open). Older versions will still be around to fork from, but maintaining a fork of an OS is a pretty large task.

Android is also open source, and is notably very difficult to simply fork and do your own thing and then actually use the thing, unless you happen to be a handset maker.

My OS entirely driven by Google? No thanks, they're making enough of a mess of the web (and Android lately, TBF).

Post reply on HN