3 ms·
Oh man! I first tried BeOS personal edition when it came on a CD with Maximum PC magazine. (Referring to same demo CD, though the poster is not me: https://arst
by rayiner 7y ago
Oh man! I first tried BeOS personal edition when it came on a CD with Maximum PC magazine. (Referring to same demo CD, though the poster is not me: https://arstechnica.com/civis/viewtopic.php?f=14&t=1067159&start=40 https://arstechnica.com/civis/viewtopic.php?f=14&t=1067159&s.... Also, how crazy is it that Ars Technica’s forums have two decade old posts? In 2000, that would be like seeing forum posts from 1980.) I remember being so happy when we got SDSL, and I could get online from BeOS. (Before that, my computer had a winmodem.)
BeOS was always a very tasteful design. And well documented! I learned so much about low level programming from the Be Newsletters: https://www.haiku-os.org/legacy-docs/benewsletter/index.html https://www.haiku-os.org/legacy-docs/benewsletter/index.html. The BONE article is a great introduction to how a network stack works: https://www.haiku-os.org/legacy-docs/benewsletter/Issue5-5.html#Engineering5-5 https://www.haiku-os.org/legacy-docs/benewsletter/Issue5-5.h.... I still have a copy of Dominic Giampalo’s BeFS book somewhere.
BeOS was very much a product of its time. (Microkernel, use of C++, etc.) What would a modern BeOS look like? My thought: use of a memory and thread safe language like Rust for the main app-level APIs. (Thread safety in BeOS applications, where every window ran in its own thread, was not trivial.) Probably more exokernel than microkernel, with direct access to GPUs and NICs and maybe even storage facilitated by hardware multiplexing. What else?
- anon9001 7y ago> In 2000, that would be like seeing forum posts from 1980. That's the premise of Jason Scott's project launched in 1998 :) http://textfiles.com/ http://textfiles.com/
- cbm-vic-20 7y agoHe also livestreams on Twitch; recently he's been streaming the archival of Apple II floppies. https://www.twitch.tv/textfilesdotcom https://www.twitch.tv/textfilesdotcom
- anthk 7y agoHaiku OS still uses C++.
- rvz 7y ago> What would a modern BeOS look like? Haiku. (0) But if you change your question to "What would a modern OS look like?" Fuchsia. (1) The only relationship that they have is that a kernel engineer called Travis Geiselbrecht designed NewOS (Haiku's modified kernel) and Zircon (Fuchsia's Microkernel). [0] https://haiku-os.org https://haiku-os.org [1] https://fuchsia.dev https://fuchsia.dev
- jbn 7y agoHere's the BeFS book: https://news.ycombinator.com/item?id=12309686 https://news.ycombinator.com/item?id=12309686
- zokula 7y agoBeOS did not use a microkernel, it was a straight-up up boring monolithic kernel.
- rayiner 7y agoPeople at the time described the kernel as a microkernel, including the O’Rielly book: https://www.oreilly.com/openbook/beosprog/book/ch01.pdf https://www.oreilly.com/openbook/beosprog/book/ch01.pdf. It ran networking for example in user space.
- gok 7y ago> What would a modern BeOS look like? There's a bit of BeOS in Android. Binder IPC is much like BMessage. And nowadays everyone puts stuff like graphics and media in a separate user space daemons, which was unusual for the time. Pervasive multithreading basically happened in the form of pervasive multiprocessing.