4 ms·
Right now it kind of reminds me of BeOS, which could do absolutely incredible concurrent realtime low latency media processing but was absolute torture to get a
by jandrese 9y ago
Right now it kind of reminds me of BeOS, which could do absolutely incredible concurrent realtime low latency media processing but was absolute torture to get a proper Web Browser working.
The problem with legacy support is that it drags in the braindamage you were trying to avoid by rewriting the OS in the first place. But without legacy support it's almost impossible to grow beyond the toy OS stage. It's the whole "So, what do I do with it?" factor.
- neuronexmachina 9y agoA couple of former BeOS folks are actually working on Fuchsia: Travis Geiselbrecht and Brian Swetland.
- agildehaus 9y agoTravis Geiselbrecht is responsible for NewOS (http://newos.org/ http://newos.org/). The kernel in Haiku, the open-source BeOS recreation, was forked from NewOS' kernel.
- abqwe 9y agoSome logs from Travis Geiselbrecht in Haiku IRC channel about Fuchsia.[1][2] Also looks like Fuchsia barrowing some code from Haiku.[3] [1] https://discuss.haiku-os.org/t/fuchsia-a-new-google-kernel-created-by-beos-developers/4161/2 https://discuss.haiku-os.org/t/fuchsia-a-new-google-kernel-c... [2] https://echelog.com/logs/browse/haiku/1471125600 https://echelog.com/logs/browse/haiku/1471125600 [3] https://discuss.haiku-os.org/t/fuchsia-a-new-google-kernel-created-by-beos-developers/4161/5 https://discuss.haiku-os.org/t/fuchsia-a-new-google-kernel-c...
- jjrh 9y agoI watched a BeOS demo video ( https://www.youtube.com/watch?v=BsVydyC8ZGQ https://www.youtube.com/watch?v=BsVydyC8ZGQ ) the other day and some of that stuff is /still/ impressive.
- jandrese 9y agoI had a roommate in college who had a BeBox with the twin PPC 603(?) processors and a row of LEDs on the front configured to show the current load of each CPU. It was super cool and could make these absolutely insane multimedia demos, but he was forever trying to get software to work on it. Whatever POSIX compatibility it had was absolutely insufficient for modern (at the time) applications. Everything required some rewriting by hand, and there were definitely crashes. Worse, Netscape didn't release a BeOS version of Navigator so he was always hacking up the latest Mosaic release to try to get it working. I was running FreeBSD at the time and it was the polar opposite. Sound barely worked, the only video players were slow and unreliable open sourced school projects, but it was front and center on the newfangled Internet thing that was going around at the time.
- contextfree 9y agofrom comments from people who worked on it (e.g., https://twitter.com/MCSpaceCadet/status/968666523425386497 https://twitter.com/MCSpaceCadet/status/968666523425386497 https://twitter.com/slava_oks/status/958908471801294850 https://twitter.com/slava_oks/status/958908471801294850 ), Microsoft seems to have reached this stage with their Midori project. This was a ground up OS project based on the usual suspects from the research world i.e. object-capability security, microkernel architecture, a new lightweight process model, memory-safe systems language, zero-copy IO etc.; the project lasted 9 years and occupied over 100 senior engineers at its peak. They tried various strategies to run it on top of Windows, run it on top of Linux, run Windows on top of it, run it on Hyper-V, etc etc. before eventually giving up.
- lambda 9y agoGoogle has the advantage of having two consumer platform (Android and ChromeOS) running on Linux, but with the majority of application code written on top of additional abstractions on top of Linux so a lot of it would still run if the appropriate runtimes were ported over to Fuchsia. Google is also developing Fuchsia openly, if quietly, giving developers a preview of where they are going. Microsoft developed Midori mostly in secret, and while we've heard a little bit about what they did in that project from blog posts and Twitter threads, nothing official has ever been released publicly. And on the server side, virtualization and containerization are huge and growing, as many people find the benefits in flexibility, repeatability of deployment, and incremental billing to outweigh the absolute overhead over bare-metal performance. Fuchsia seems to support virtualization as a core part of the API, allowing you to run Linux VMs when you need to, and it could be possible to port containerized applications piecemeal to Fuchsia with some components still running on Linux on co-located or even the same hardware. I feel like this is one of the benefits of the relatively simpler POSIX style API design, and extensive use of sockets for IPC, over the fairly complex, heaviweight Win32 API and NT kernel. I feel like a lot more software that runs on Linux (and is generally portable to several other POSIX-ish OS's) would be a lot easier to port to Fuchsia, and in an incremental way, than all of the software that runs on Windows systems would be to port to Midori.
- pjmlp 9y agoThey did not gave up, management pulled the cord on the team. Joe mentioned at his Rustconf talk how hard it was to convince the Windows team, even with the system running in front of them. When people are religiously against something, no amount of technical achievements is going to change their mind.
- hollerith 9y ago>BeOS, which could . . . but was absolute torture to get a proper Web Browser working. Ah, but that is exactly why I'm paying attention Fuchsia even though in general I ignore new OSes: it would not be hard for the organization behind Fuchsia to instruct the 1000-or-so developers it employs who maintain a web browser to make the web browse runs on Fuchsia. (and it is open-source).