Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google’s Fuchsia OS on the Pixelbook

arstechnica.com

Post reply on HN
Print view View original

121–126 of 126 posts

Re: Google’s Fuchsia OS on the Pixelbook

#121

Post by steveklabnik »

peoplewindow wrote: post #115
greenhouse_gas wrote: post #35

Earlier quoted context omitted.

Just want to point out that not that long ago redox-os (the microkernel OS in Rust) asked people to test it. People were able to kernel panic it, get privilege escalations, and DDoS it. In short, it had the same same issues a C based kernel would get. It's true that it's still heavily in development and doesn't offer any guarantees whatsoever, but I think that it should be pointed out that just because your language…

Can you link to that? I'd be curious to see how they did those things. I guess Redox has a lot of unsafe Rust code?

Safe rust doesn’t mean “no bugs”, these kinds of issues aren’t inherently memory safety issues, they can also be the product of logic bugs.

Re: Google’s Fuchsia OS on the Pixelbook

#122

Post by bitmapbrother »

Sir_Cmpwn wrote: post #31
liuw wrote: post #17

Earlier quoted context omitted.

Why focus on the language and the possibility of a million and one bugs but not the architecture and design choices?

Because it's an easy indicator of someone who has no idea what they're doing in OS development. Choosing the wrong tool for the job is meaningful. Have you ever looked through Chromium's C++ codebase? The same people are working on this and it tells us that they haven't learned their lesson (or they want to tightly integrate Chrome with Fuschia, which is also a foreboding sign). Edit: I should clarify that I think C…

>Because it's an easy indicator of someone who has no idea what they're doing in OS development. Choosing the wrong tool for the job is meaningful. Have you ever looked through Chromium's C++ codebase? The same people are working on this and it tells us that they haven't learned their lesson.

Have you looked into the backgrounds of the main developers working on Fuchsia OS? Because if you had you would have discovered that that they have a rather impressive resume who actually know what they're doing.

Travis Geiselbrecht - BeOS, iOS, Hiptop OS, Little Kernel

Brian Swetland - BeOS, Hiptop OS

Chris McKillop - a member of the original iPhone team, WebOS, QNX OS, Hiptop OS

Re: Google’s Fuchsia OS on the Pixelbook

#123

Post by Sir_Cmpwn »

bitmapbrother wrote: post #122
Sir_Cmpwn wrote: post #31

Earlier quoted context omitted.

Because it's an easy indicator of someone who has no idea what they're doing in OS development. Choosing the wrong tool for the job is meaningful. Have you ever looked through Chromium's C++ codebase? The same people are working on this and it tells us that they haven't learned their lesson (or they want to tightly integrate Chrome with Fuschia, which is also a foreboding sign). Edit: I should clarify that I think C…

>Because it's an easy indicator of someone who has no idea what they're doing in OS development. Choosing the wrong tool for the job is meaningful. Have you ever looked through Chromium's C++ codebase? The same people are working on this and it tells us that they haven't learned their lesson. Have you looked into the backgrounds of the main developers working on Fuchsia OS? Because if you had you would have discovere…

Someone said something similar earlier, but I chose not to respond to avoid getting deeper into an unrelated argument. The short of it is that I don't find BeOS (and Haiku) particularly impressive. WebOS is all userspace and I don't really care how Fuschia's userspace looks, and I have to admit I don't know much about QNX or Hiptop.

Re: Google’s Fuchsia OS on the Pixelbook

#124

Post by vxNsr »

tensafefrogs wrote: post #37
vxNsr wrote: post #7

I find it fascinating how polished the UI is even as it's missing core features.

The UI is made with Flutter, which can be used for Android & iOS apps today: https://flutter.io/

Thanks, that's a cool tool I've begun playing with it and it seems to simplify a lot of the difficult parts of creating good looking UI on mobile.

Re: Google’s Fuchsia OS on the Pixelbook

#125

Post by sebe »

happyguy43 wrote: post #57
SllX wrote: 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…

Fuchsia docs says POSIX lite and Web runtime, under Backwards compatibility. More info at https://fuchsia.googlesource.com/docs/+/HEAD/book.md#zircon-... You can fire up the fuchsia in qemu, as it requires hardware graphics, you can't run the desktop, but you can have multiple shell open. I've had a play and it has vim and sql_shell and a bare bones top.

Re: Google’s Fuchsia OS on the Pixelbook

#126

Post by UncleMeat »

willtim wrote: post #102
fooker wrote: post #97

Earlier quoted context omitted.

In line with your reasoning, software development methodology has significantly improved over the years. One does not write C++ in 2018 as they would have written C in 1980.

Best practice has changed, but C++ does not enforce it. Did Samsung follow best practices with Tizen? Languages like Rust and Haskell are an attempt to put such best practice into the language tooling.

You'd have to be insane to want to implement an os in Haskell.
Post reply on HN