5 ms·
I think that now that we have a language suitable for writing kernels, we also need to have a discussion about what do we really want from a new os. Over the y
by adamnemecek 10y ago
I think that now that we have a language suitable for writing kernels, we also need to have a discussion about what do we really want from a new os. Over the years there have been quite a few OSs and some of them were more advanced than the currently popular OSs. E.g. AS/400 didn't make the distinction between memory and hdd which seems to me like a good idea. BeOS has a fully async API which resulted in a much better user experience and better CPU utilization. Tandem had erlang like processes. None of the popular OSs have this. I'm not sure I want another UNIX implementation.
Furthermore, why are all the APIs so diverse? Why aren't there reactive operating systems (as in OS with reactive API)? All of these ideas can be explored in Rust but on some level I'm not sure what should be the feature set of the OS of the future.
The current driver models aren't that great either.
- TickleSteve 10y agoWould be wiser to only change one variable at once... Prove that an existing RTOS style library can be written with a simple scheduler working well. That would go a long way to it gaining adoption in the embedded world, show that traditional solutions work correctly with the new language first.... then move on to an innovative OS.
- adamnemecek 10y agoSometimes you have to go top to bottom. I think that Alan Kay says something along the lines that you should start with the design of the API. Polya say something similar in how to prove it.
- taeric 10y agoPolya says to start from the solution. The problem is you have to know a definitive solution for this to be applicable. In the case of this hypothetical OS idea.... Most of what people "would want" from an OS is a made up thing they can't really express. There is no working backwards from a generalization. You work backwards from concrete ideas. Realistically, the OS everyone wants is "one that runs all of their software." They would prefer one that "doesn't crash." However, starting over with no real software is a non-answer.
- adamnemecek 10y ago> Realistically, the OS everyone wants is "one that runs all of their software." I want an OS that's easy to program to the point I don't actually have to rely on third party software too much. This might be a pipe dream but I'm not convinced it's not achievable on some level. > They would prefer one that "doesn't crash." However, starting over with no real software is a non-answer. I'm trying to open a discussion about what ideas have been tried in the past, seem good, but for one reason or another didn't catch on.
- taeric 10y agoHow does any modern computer not fit this ideal? Linux, in particular, is very easy to start hacking at.
- adamnemecek 10y agoWhat percentage of the OS that you use every day was written by you?
- taeric 10y agoWhy would I even want that? Like, seriously. How much of the computer could I even make? I even studied this stuff in school and understand the basics. Somewhat beyond the basics, actually. Still, I would have zero capabilities to make my own. Move that to other areas. My car? Forget about it. I could have a fighting chance at building a bike. However, to build a good one, not a chance. So... why is this something that is even desirable in the computer? Now. Do I want to be able to fix what I can? Of course. I run emacs, in part because I like that I can pull up the source, quite easily, of any component I am using. I still rely majority on code written by others. And have no shame or concern in doing so.
- adamnemecek 10y ago> Still, I would have zero capabilities to make my own. That's the point, you don't have much capability to alter the OS you are running. But you should. It's not unachievable but the languages, tools and OS (and maybe HW) have to come together to allow for this. > Move that to other areas. Computer is different from any of those since it's fundamentally a machine to model human mind. I always feel like my OS is somewhat restrictive as to what it lets me to do easily and what alterations it lets me to make. > Now. Do I want to be able to fix what I can? Of course. I run emacs, in part because I like that I can pull up the source, quite easily, of any component I am using. I still rely majority on code written by others. And have no shame or concern in doing so. Right. But the languages and tools that we use currently don't lend themselves to terseness and correctness. I think that that's the direction of future languages.
- BinaryIdiot 10y ago> The current driver models aren't that great either. Driver developer is soooo far out of my frield but it's always fascinated me. I'm curious why hardware companies didn't go with something like an interface for products versus these highly complex drivers; wouldn't it be possible for each type of device a group comes together, decides on an interface, and now anytime you plug a device in it would work (and if a specialized driver could be better you could install that separately but the goal is making everything magically work, immediately). But since no one has done it I feel like my idea is either horrible or short sighted. But I do want to look into how it all works one day.
- stusmall 10y agoYou aren't shortsighted, they have. Look at USB class drivers.
- deleted 10y ago[deleted]
- sedachv 10y agoThat is how the original IBM PC BIOS worked with basic hardware, more or less. Both Open Firmware (https://en.wikipedia.org/wiki/Open_Firmware https://en.wikipedia.org/wiki/Open_Firmware) and EFI (http://www.uefi.org/sites/default/files/resources/EBC_Driver_Presentation.pdf http://www.uefi.org/sites/default/files/resources/EBC_Driver...) include a bytecode interpreter for portable device drivers - the idea is that the hardware device stores the driver as bytecode, the Open Firmware controller loads that driver bytecode when the device is plugged in and uses the CPU to execute it, and provides a uniform API to the OS. From what I read EFI was developed at Intel to be a deliberately incompatible Open Firmware clone for the Itanium. There really is not that much savings or advantage to this approach so there are not a lot of Open Firmware and EFI drivers out there. You really do not want hardware manufacturers writing drivers either - they tend to be terrible and full of bugs. Having the manufacturer publish the hardware specifications so that drivers can be easily implemented by developers is a much better approach, sadly a lot of manufacturers cannot be bothered with this.
- wott 10y agoDuring DOS days, standards or more often de-facto standards had appeared. So chip makers or board makers would make their chip or board compatible with another existing model, and you would just need one driver per kind of device to get most of the expected functions. I am thinking of : -- sound cards being compatible with AdLib and/or SoundBlaster and/or SoundBlaster Pro; -- network cards being compatible with NE2000; -- video cards being compatible with VESA standards. Then Windows took over, buses changed, the shitfest started and never stopped. And now the shitfest comes with NDAs too.
- paulsutter 10y agoSecurity.
- xj9 10y agoGenode on seL4.
- bluejekyll 10y ago> Why aren't there reactive operating systems (as in OS with reactive API) This is something that's been interesting me lately. I've been working with the excellent futures and tokio libraries, and I've wondered what would it be like if that was the primitive for all OS interactions? Basically, imagine a message passing system like Mach, but where the fundamental messages are all futures based. There might be some interesting things possible without holding locks in the kernel.
- phil-opp 10y agoI definitely plan to integrate the futures library in the kernel somehow. We just need some asynchronous things and threads first :).
- bluejekyll 10y agocool! Do you have an overarching design your working off of? Or still too low level?
- phil-opp 10y agoI have some vague ideas for the next posts, but no overarching design. At our current level, there aren't many design choices anyway. It will get much more intesting when we create a threading/concurrency model in the future.
- legulere 10y agoIMO a sane syscall API that was built with sandboxing in mind. The unix API gives you access to basically all of the computer or at least all of the user's data. Nowadays we live with executables we can't trust. Random binaries don't need to be dangerous to execute, only the syscalls that they can make on windows and unixes make them dangerous. This also relieves you from the need to sign most programs by a central authority
- pjmlp 10y ago> I think that now that we have a language suitable for writing kernels We already had it in 1961 as ESPOL and NEWP. http://www.liquisearch.com/burroughs_large_systems/algol/espol_and_newp http://www.liquisearch.com/burroughs_large_systems/algol/esp... Followed by many others, before UNIX's adoption due to its source being available for free. > I'm not sure I want another UNIX implementation. Yeah, they just keep repeating what was already done and without much research besides adding mainframe features. As Rob Pike puts it: "We really are using a 1970s era operating system well past its sell-by date. We get a lot done, and we have fun, but let's face it, the fundamental design of Unix is older than many of the readers of Slashdot, while lots of different, great ideas about computing and networks have been developed in the last 30 years. Using Unix is the computing equivalent of listening only to music by David Cassidy." from https://interviews.slashdot.org/story/04/10/18/1153211/rob-pike-responds https://interviews.slashdot.org/story/04/10/18/1153211/rob-p... What we really need are OSes that take the ideas from human-computer interaction from Xerox PARC and Viewpoints Research Institute and take them further into mainstream, using safe languages in the process.
- DblPlusUngood 10y ago> "...while lots of different, great ideas about computing and networks have been developed in the last 30 years." > What we really need are OSes that take the ideas from human-computer interaction from Xerox PARC and Viewpoints Research Institute and take them further into mainstream, using safe languages in the process. How are modern OSes prevented from using said ideas (which ideas exactly?) simply because they are a UNIX implementation?
- pjmlp 10y agoBecause most UNIX users see only this: http://pubs.opengroup.org/onlinepubs/9699919799/ http://pubs.opengroup.org/onlinepubs/9699919799/ Everything else is fluff, and could stay just like it was on UNIX System V. Hence why for macOS, iOS, tvOS, Android and ChromeOS, having an UNIX kernel is just a matter of convenience, given their application models and programming languages. Apple and Google could eventually migrate to something else as kernel while keeping their Objective-C, Swift, Java and JavaScript APIs. NeXT based NeXTStep on UNIX as a door into the then new UNIX worksations market, but it never had a CLI culture like the other UNIX vendors. GUI workflows like on Xerox PARC were always important to Steve.
- _pmf_ 10y agoOff the top of my head: - strongly typed syscalls. - easier way to circumvent the kernel / OS (unikernels are very active and tangible space, see HFT) while potentially staying relatively safe - safe zero copy IPC - projects like https://zinc.rs/ https://zinc.rs/ which fold Embedded Linux' Device Tree concept into a coherent declarative HW description that is consumable by the bootstrapper
- justaaron 10y agoI would like to see a very simple OS, built for single-usage, allowing a singular application full control of hardware resources (multi-"threaded", but then let's expose "kernel threads" and "processes" via a rather simple/brutal/direct scheduling API.) I basically want a simple RTOS and HAL/Driver body. I want timers and clocks. I want some block devices and perhaps file-system-primitives etc. I want TCP/IP and a USB stack. I don't want anything nearly as complex as a Unix, nor need it be Posix compliant etc. I would like it to be runnable from uboot, as it's ARM time now, and arm64 support should be a given. I would think there is a substantial market for a minimalistic ultra-simple braindead-easy alternative to the "embedded linux" (LOL) wave that seems to be proliferating on all "a" class arm processors... i need determinacy more than thoroughput, but a 64k ram microcontroller with 500mips isn't going to cut it either. there is a serious hole in the OS market for CPU's where *nix is overkill or unsuitable (and no, RTAI nor a realtime patched kernel count. the complexity of the entire codebase is still there) I've heard about MirageOS from the oCaml people, but I have not been able to find out any info about timing and concurrency etc... any info on edgy projects highly appreciated, please!