4 ms·
I'm suprised to find people surprised at the development of a new OS. Linux is around 30 years old; Unix and C are around 50 years old. Eventually the paramete
by wolverine876 5y ago
I'm suprised to find people surprised at the development of a new OS. Linux is around 30 years old; Unix and C are around 50 years old.
Eventually the parameters of the world and of user needs shift far enough from the original design that it's less expensive to develop something new than to adapt the old thing. Sometimes it's impossible to adapt the old thing: for practical purposes, no amount of work will make C secure.
EDIT: Apparently Fuschia uses C and C++, and uses them exclusively in the kernel (if I understand correctly), and Rust and Dart are permitted for some uses, if this document is up-to-date:
https://fuchsia.googlesource.com/fuchsia/+/refs/heads/main/docs/contribute/governance/policy/programming_languages.md https://fuchsia.googlesource.com/fuchsia/+/refs/heads/main/d...
It's an impressive run, but the ground has shifted, slowly, under our feet, and now Unix/Linux are no longer a good fit. Let's not be conservative; let's do what our smarter predecessors did and embrace change.
Fuschia is free and open source, per other comments in this thread. If that's true, let's be very thankful that the successor to Unix, if that's what Fuschia becomes, is FOSS. If Google put a proprietary OS on its phones, etc., even if they didn't charge for it, they'd have a lot of market power and they'd be competing with a 50 year old OS. It could be a terrible blow to FOSS.
- amelius 5y ago> It's an impressive run, but the ground has shifted, slowly, under our feet, and now Unix/Linux are no longer a good fit. Unix is still a good fit for a kernel; e.g. it is used by Apple. The stuff built on top of the kernel (UI, etc.) can change, of course.
- jcranmer 5y ago> Unix is still a good fit for a kernel; e.g. it is used by Apple. The POSIX APIs are not a good basis for designing a kernel. There are plenty of areas where it's widely agreed that the APIs are fundamentally utter garbage: POSIX signals, filesystem ACLs, async I/O, select, IPC. Arguably even some of the more less garbage APIs (e.g., regular filesystem calls) are extremely detrimental towards writing good software--imagine if we had filesystem APIs based on semantics such as "atomic file write" or "append-only files" (that guaranteed that a reader would only see old or new versions, not partly-written versions) instead of what we have now, where people attempt to recreate those APIs in userspace.
- curt15 5y agoWindows NT has far more advanced facilities for async I/O [1]. [1] https://stackoverflow.com/questions/5283032/i-o-completion-ports-advantages-and-disadvantages https://stackoverflow.com/questions/5283032/i-o-completion-p...
- johncolanduoni 5y agoIt did, then io_uring leapfrogged it, and now Windows is moving towards adding a ring-based IO submission system: https://windows-internals.com/i-o-rings-when-one-i-o-operation-is-not-enough/ https://windows-internals.com/i-o-rings-when-one-i-o-operati...
- pjmlp 5y agoUNIX as used in macOS isn't the classical UNIX kernel, and since the last 5 years Apple has been moving away from it. Want the new networking APIs? They are exposed only to platform frameworks not POSIX.
- m4rtink 5y agoGiven that Fuchsia is not GPL licensed (making proprietary forks possible & likely) and apparently developed behind closed doors, not by a self sustained community like the Linux kernel its not very far from your worst case scenario, especially if Google starts force feeding it into Android like it did with many non GPL and proprietary licensed software over the years.
- runeks 5y agoI wonder how much GPL actually protects against proprietary forks. Aren’t most of these driver vendors in China where Google would have little recourse if GPL is violated?
- m4rtink 5y agoWell, at least it makes major vendors cooperate - for example a lot of modern Sony PlayStation hardware runs heavily modified FreeBSD, yet anything the project ever got back from Sony is IIRC some multiprocessing improvement patches. Also the multitude of companies contributing together to the Linux kernel are often direct competitors. Yet due to the GPL all their contributions are available to everyone else - so even though you are technically helping your competition, they have to do the same thing for you. With permissive license, you competition can take the code and run with it, never contributing anything back, kinda like how Sony did in the example above.