To anyone who hasn't already: I really recommend checking out Haiku OS [1], the FOSS successor to BeOS. It's so pleasant to use and supports a surprisingly large catalog of software.
Claude built me a meta web/notes/code search engine with IOS and MacOS apps, and for fun I asked it to make a Haiku version [1], which it did in under 20 minutes.
With AI I feel like a lot of these bygone-era OS's could see a whole new ecosystem of modern apps within a very short period of time.
At this point, they could likely decompile MacOS classic and rework it to give it modern memory protection, virtual memory, preemptive multitasking, and networking.
I am in the middle of doing this with apple's System 6 and adding a posix-compliant shell under the codename bluetail, and working my way up, i've got it booting with an os, busybox, openssh and stuff. Boots on a raspberry pi 3 A+ bare metal (And qemu, of course). And full usb MIDI support, because (I said so, and) there's actually an incredible catalog of early DAW software that will run on System 6. And pretty decent usb ethernet, sound, webcam etc etc. The future of hobby software is wild.
68030 on a 16-bit bus, max 10MB RAM, no expansion slots so nothing except SCSI.
So, I put 10MB in it, a bigger SCSI HDD, a SCSI Ethernet adaptor on the back, and built both OSes up from scratch.
MacOS 6.0.8 with all the extras: a menu bar clock, hierarchical Apple menu with modular Control Panel, MacTCP, etc.
And MacOS 7.6.1, which doesn't officially support the Classic II as it wants 12MB RAM minimum -- but I had RAMdoubler. OpenTalk, Netscape Navigator 3, Communicator 4, some early Internet Explorer, etc.
Honestly, there was little difference. It was usably quick on 7.6.1 and more stable. So many things that are extras on 6.0.8 are built in to 7.x that it doesn't need that much more disk or memory.
7.x did more, made it easier, and ran well.
But, as an example, on roughly 1MBs ADSL, it took about half an hour to render the top-left quarter of https://slashdot.org/.
Perfectly usable machine, could do email, FTP, Gopher, but forget it on the WWW on of the noughties (2000-2009).
Well the parent commenter said "SE era machines". That era of machines (Plus, SE, Classic) had an 8 MHz 68000 and only supported up to 4 MB of RAM. The Low End Mac page you linked says that your Classic II is 1.8x faster than an SE. On the 68000 Macs, System 7 (especially 7.1 and 7.5) feels a lot more sluggish than System 6, and will use over half the RAM just running the OS with no applications. Being able to skip the "extras" you mention that became mandatory on System 7 is useful when you have a slow machine with limited RAM. Of course I'm not sure what any of this has to do with running the OS on a Raspberry Pi.
Get a gopher client and join gopher://hngopher.com (r/o HN over gopher), gopher://magical.fish (huge portal, from a translator from text adventures over gopher, and even current news) and gopher://sdf.org. (blogs).
How did you implement that? Is it like a modified emulator with your enhancements added? How does the System 6 cooperatively multitasking stuff interoperate with the posix stuff?
> they could likely decompile MacOS classic and rework it to give it modern memory protection, virtual memory, preemptive multitasking, and networking.
It had most if not all of that.
It had networking from the start with AppleTalk, later Ethernet and internet with MacTCP.
MacOS 9 had a preemptively scheduled kernel.
The problem is having that and supporting the software ecosystem, which depended on cooperative scheduling without having memory protection.
MacOS 9 ‘solved’ that by running the classic OS in a single process. It had APIs for creating preemptively scheduled threads, but those threads were limited in what they could do.
> You are describing attributes of the NeXT-based OS X but calling it MacOS 9.
You're mistaken.
> MacOS 9 [had] no preemption
Classic Mac OS has had vertical retrace (VBL) interrupts since System 1.0 (which are a form of preemption). But suppose we disregard that.
>> MacOS 9 had a preemptively scheduled kernel.
The GP is correct. Applications run cooperatively within the Blue task, but the Blue task itself runs preemptively with other MP tasks (which an application can create).
I know about the nanokernel, yes. Without following the links, Gary Davidian (is that spelled right?) did amazing work.
Very very little used it. About the only classic app I ever heard of that could even use pre-emption and background execution were some demanding Photoshop filters. Enough that Daystar Digital built multiprocessor Mac clones just for that alone:
It's totally fair to disagree about whether Mac OS 9 meets the stated requirements. I just don't think it's reasonable to assert that GGGP (who may have made unwarranted claims about OS 9) was actually confusing OS 9 with OS X.
> At this point, they could likely decompile MacOS classic and rework it to give it modern memory protection, virtual memory, preemptive multitasking, and networking.
You'd lose compatibility with the applications, though, so you'd have to decompile and rework those as well. And even if you did, you couldn't legally distribute any of it.
An alternative approach is high-level emulation. Running a separate instance per application gives you process isolation (via the host OS) for free.
> I assume booting an OS with a mere few megabytes of RAM footprint would only take milliseconds?
I occasionally spin up VMs with this and OS2. I miss the era of operating system options. But but linux. It has it's place, I run FreeBSD, but for desktop, options dimish. I like apple hardware, I like apple hardware trackpad support. Running Linux on a MacBook is not something I would ever do. I used FreeBSD on stinkpads for years.
I loved my BeBox, but what would be the modern equivalent of the GeekPort? I've been using esp32/nRF52/etc boards for uart/spi/i2c/i2s/pwm-type work... it feels like hardware hacking on a desktop is a lost art.
The old school way to do I/O on desktop was via the parallel port, which I imagine would still work if you get a PCIe parallel port card. For a more modern way, the FT232H chip supports UART, SPI, I2C, JTAG and raw GPIO over USB, and there are break-out boards available.
I was going to say this as well the GeekPort was a parallel port. I always thought it was marketed that way is that Macs didn’t have a parallel port. Having a parallel port would make the spec sheet seem regressive. I believe serial ports were always faster than parallel ports.
I bought a BeBox at the time.
The original Nike store in NYC purchased one to do their signage media playback. It didn’t go well.
Your BeBox case was lovingly spray painted in a conference room with inadequate ventilation by us at Be at corporate HQ in Menlo Park. Each one was lovingly assembled by the actual people who designed the hardware and wrote the code.
Some former Be employees have commented here in the past saying that Apple made the right decision to buy Next from a technical perspective, as BeOS had poor code quality and was far behind NEXTSTEP in important areas like networking and printing. They also implemented the OS API directly in C++, which tied them to a specific C++ compiler (some mid-90s version of GCC) due to the ABI getting broken in newer versions. The 32-bit version of Haiku (modern BeOS reimplementation) supports BeOS software, and as a result still needs to be compiled with that mid-90s GCC release.
Beyond that, I'm not sure if buying Be would have fixed the managerial problems at Apple. Would they have been able to add the required features to BeOS to turn it into a production OS without the project turning into another Copland? Would the existing Apple management have slimmed down the massive Apple product line that had dozens of nearly identical models? Would it have gotten rid of dead-end projects like Newton and Pippin? Etc.
Pre-standard C++ is an even worse programming language than C++ 98, but also the big difference wouldn't have been the technology, it was the people. If Apple buy Be Inc they're getting JLG back whereas if they buy NeXT they get Jobs back.
Jobs is what makes or breaks Apple in that critical period. I didn't like him but that's relevant to the success of the company. JLG did not have whatever it was Jobs gave the company.
And Jobs brought an entire team of people with him. Many of the top people at Apple got replaced by people from NeXT. Avie Tevanian, Craig Federighi, Bertrand Serlet and many lesser known names came from NeXT. The joke at the time was that NeXT bought Apple for -$400M.
Yes, the reverse acquisition. Minor correction though, Craig didn’t show up until much later. He missed out on some very tough years and came on when Apple was fully revitalized and printing money. I might even suggest what I consider the decline of Apple software occurred when Avie and Bertrand left and Craig took over.
It was reported that Apple offered $75M for Be and almost $500M for NeXT and in retrospect those seem like entirely fair valuations. One was a mature OS and the other was a demo of an OS.
JLG countered with a $100 million and I thought Apple offered Steve $400 million at first. There was a moment when Apple was just talking to us (Be) and Steve heard about it. Bummed.
Best example of how far BeOs fell short was that for a very long while it lacked printer drivers of any kind --- by contrast, not only did NeXTstep essentially get printing "for free" since it used Display PostScript, the implementation of that was such that Adobe demanded a modification to the user agreement limiting the output resolution so that print shops would not be able to purchase NeXT computers and use them as RIPs for imagesetters.
Former Be person here. Excellent summary. To further elucidate the management issue, some of the Be management went to Palm and they weren’t super effective there either. A fun alternative universe would be Apple buying Be, Apple going bankrupt or eaten by the clones, NeXT powering the internet with WebObjects, Microsoft crushed by antitrust and we are all running Linux using Eazel/GNOME.
Yeah it's interesting how similar what happened with Palm OS 6 was to Copland. They had a working, but outdated OS that had been hacked onto a new platform as a stopgap, then they couldn't get the rewrite meant to take full advantage of the new hardware out the door. Palm OS 6 was at least finished, but it never got used in a shipping device. There's an interesting Reddit post going over how the OS design was fundamentally flawed when combined with the ARM processors that were available at the time: https://www.reddit.com/r/Palm/comments/1422bqy/palm_os6/jn5o...
One minor correction: the Haiku developers worked some magic with GCC binary compatibility and modern Haiku builds are done with a modern GCC yet still preserve the ability to run and interoperate with software built using the old release which is important for preserving the use of commercial software built for BeOS without released source code.
I recall the C++ "fragile base class" problem already starting to rear its ugly head by the end. Existing base classes couldn't be reasonably extended without breaking compatibility with existing applications, and the BeOS API was routinely designed in a way that promoted subclassing. e.g. to implement a window, you'd subclass BWindow and fill it with your own subclasses of BView. It's difficult to see how they would have dug themselves out of this hole in the long term.
I'm not familiar with Be API, but I did a lot of GUI dev in Java Swing back in the day. It's not that hard in principle, you launch whatever background op in whatever threads you like, and any GUI updates have to be done by sending messages back to the GUI event thread (or something like Swing.invokeLater(closure)).
Yes, Be GUI is heavily multithreaded, so core dumps were kind of common, and stuff like Swing.invokeLater(closure) only came later in Swing, after existing for a while as community library, after folks having the same issues in Java GUI applications.
Note that on Android they took an hammer solution, programming patters to invoke such code on main thread, have as outcome that there are either lint compile errors, or platform killing the application, for those flows not verifiable at compile time.
Yes, and it’s been a quarter century or so but this is how I remember BeOS doing it. Every window got a dedicated thread for handling events and GUI updates, and other code would communicate with it via message passing. The OS had a standard message passing system that was pervasive; if I remember right every thread got a mailbox by default.
But it was 90s era C++, so probably that was all just a polite agreement and the reality was that circumventing the message passing to directly call methods on objects that belong to other threads was common, and just as likely to happen by accident as on purpose.
Outside of the GUI, Be is a very thin veneer over Unix. There is, no joke, a class named "BStatable" which, if you know some Unix, is just stat, because of course what their OS kernel implements is just stat.
In the places where there's something entirely different going on, such as networking in earlier BeOS, it's trash and you'd obviously want to throw it away and do what Unix did - Be were doing so. So a hypothetical turn of the century fruit-flavour BeOS is probably much closer to "Unix with a different UI" than you're thinking. NeXT changed nothing there.
A strong BeOS selling point was that it was POSIX compliant. I guess that is what you mean by a thin veneer. But we had to write all that code; it wasn’t like we were running Linux or some SCO or other flavor of Unix. It was a written and rewritten and rewritten multiple times.
I am greatly enjoying the juxtaposition of a comment asserting that obviously BeOS was so far from POSIX that Haiku had to do loads of work to get there and your comment that BeOS was POSIX compliant.
Haiku is all new source, so they had to figure out how to get the binaries to run. I am not the POSIX expert, but I think it was just an API guarantee not ABI.
There were several companies that had the BeOS source and that source can be found in the wild. It is speculated that yellowTAB ZETA was based on unlicensed BeOS source code.
It would have been a disaster, BeOS was significantly different from a NeXT/BSD-like unix type base that made it relatively easy for software to be developed on MacOS in the 10.0 to 10.4 era. Early versions of MacOS X like 10.0 were clearly just an evolved NeXT with a cute MacOS finder like skin on top.
Well, not only former Be but former Finder developer here. The OSX Finder was certainly not a cute Finder-like skin, it was in fact huge amounts of the OS9 Finder source code including a complete copy of a modified Metrowerks PowerPlant C++ framework underneath it all. There was even elements of the old MacApp framework there. It was not a skin; it was a source code behemoth with massive amounts of legacy code.
I didn't mean that the 10.0 finder was a reskinned NeXT GUI file management application (as you point out, it clearly wasn't and was a huge thing that had a bunch of heritage code), but that the entire 10.0 GUI was a kinda-MacOS-9-like GUI on top of the NeXT bsd-heritage unix-like base. If you were to take a 10.0 system and put it side by side for comparison with the CLI environment perspective, file tree, system libraries with the last NeXTSTEP releases or rhapsody.
I hear you. Yes, the 10.0 Finder had swaths of commented out code and missing features that were present in 9. Spring loaded folders comes to mind. They came back at some point.
That is amazing to read. I never knew. I thought it was Workspace Manager, adapted to feel more Mac-like. There is even a clear line of descent:
1. The Rhapsody developer previews, which are NeXTstep with a menu bar at the top and desktop icons, and a Platinum skin.
2. Mac OS X Server 1.x which has cascading finder windows, an icon view by default, and some other things much like that.
3. Mac OS X 10.0, which I used, or tried to use, as a daily driver, with a broadly Mac-like experience with an Apple menu, but with app names next to it containing global "about" and "quit" options, and so on.
It never did acquire any of the nice stuff that came in with System 7 (e.g. drag-and-drop customisable Apple menu stored in folders in the System Folder) or MacOS 8 (e.g. folder drawers that shrink to tabs).
Right. There were several interesting skins and Finder-esque modifications of Workspace Manager. You may have seen a “Beaker” build of OSX with that. The Kodiak pre-release had the C++ Finder that is still the current Finder with PowerPlant replaced by HIView and some code refactored to use AppKit. No SwiftUI though!
Yeah, a lot of those “blue” features never were adopted or came back. The whole spatial Finder concept was lost.
> The distinctive tabbed window titles look neat, but they have a reduced draggable area, so I’d have to think harder every time I wanted to move a window.
Now imagine macOS progressing to the point where title bars have been replaced with toolbars, and buttons no longer have borders, so you have to guess what part of the window will drag it.
The feature those provide isn't immediately obvious in a static screenshot, the tabs are "magnetic" and you can take your "word" application and "stick" it's tab next to your email tab, and now you have a "tabbed application" with the email app tab on the left, and the word app tab on the right. You might have one "window" that is your front end dev workflow (firefox, vscode, 2-3 term windows) with 5 tabs, and then a second window that is your backend workflow of vscode + 4 terminal tabs, and a database workflow that is pgadmin + 2 terminal tabs. For example. I haven't seen anything like it, and I'm not sure how it handles windows with a smaller fixed window size, like winamp.
Yep, reeeally nice feature, used it on Linux. After that I wondered why apps bothered to implement their own tabbing when you could just stack Windows as tabs (assuming more WMs would adopt that feature).
It would just stack the windows of different sizes, so if you hit the Winamp tab the smaller Winamp tab would be at the top of the stack. Pretty simple and intuitive.
Haiku made them magnetic. In classic BeOS you had to hold shift and manually drag the tab over from the left. And they wouldn't be tethered together: moving one wouldn't move the other. It was annoying enough that I never bothered. By the end of BeOS's life I was mostly using the Mac OS 8 titlebar style (accessed by holding down all the modifier keys and pressing the Be menu).
I really like the linux solution here. My windows have no titlebar/borders at all. To move a window hold the window key and drag the window from anywhere, to resize hold the window key and right-click drag.
Yeah I do this too, though on macOS (through Rectangle, the window manager). Control+Option drags the window under my cursor. I picked that up from the Super key drag on Linux
I wrote something to do this 13 years ago, someone picked it up after 6 years of inactivity (since I don't own a Mac anymore): https://github.com/justjake/metamove
How funny, this is exactly the control scheme I ended up with for a window-manager-esque system I was working on recently. I love finding out I've rediscovered something proven to work well :)
I always thought the tabs would have gotten expanded functionality if Be had survived. Like they could snap together or something. IIRC they looked cool but didn’t have any real advantage.
To me it's not nostalgia, the system felt truly great to use. Haven't met anything as good since then.
And while I agree that Steve Jobs and Next were the right business (and people) choice, I still mourn the loss of a much better UI (never been a fan of the Mac UI, and it's my daily at-work system).
To me BeOS was and is still the best looking desktop OS ever, and it was so fast, it felt so good. I think in 2000ish (when it was released freely) I used it on my PC pretty much exclusively for a few months.
GNOME 3 was trying to built a clean modern minimalist desktop without all the clutter inherited from the design of Windows... But all they know is, very visibly, Windows and KDE.
RISC OS is that clean legacy free desktop. It's unlike anything else, built from scratch by a team not interested in what the rest of the world was doing.
And it's still alive and still updated and works well on modern hardware. Several separate efforts are building 64-bit replacements today.
It runs on all Raspberry Pi models up to the 4, and runs really well. As of version 5.30 it supports the Wifi chip in the Pi so it can connect to WLANs.
The owners of the IP are RISC OS Developments Ltd (ROD) and they have an enhanced version -- free on the Pi -- called RISC OS Direct, with an IPv6 stack and a modern WebKit browser:
There is another fork of the OS that is still proprietary. That's owned by 3QD. They used to sell upgrades for real Acorn-compatible kit but there's none of that that isn't vintage now, so it focuses on a software emulation that runs on modern x86 machines:
Search the Reg for "riscos" and you'll find interview with the original core team, looks at the last couple of FOSS releases, the Moonshot effort to go 64-bit and more.
Many people might not know that ARM the company behind pretty much all phone CPUs (at least historically) was founded as Acorn Risc Machines and built their own computers with their own RISC OS.
I know almost nothing about it, so I will give your links a read.
> I wish that there was some edict from KDE Project management telling everyone working on the Plasma desktop to spend a week in Haiku or something.
The other thing is that it says right at the start of the BeOS Book - and this is carried across to Haiku - is that you shouldn't have a spinner or hourglass. It should do *something*, it shouldn't make you wait.
For those who like BeOS, please check out V OS - https://v-os.dev/ - it's a Linux distro that is porting Be GUI and SDK to run on the Linux kernel. It's quite light on the resources. With enough support, it could one day be a really great alternate to Gnome and KDE on Linux.
107 comments
[ 2.0 ms ] story [ 16.6 ms ] thread[1]: https://www.haiku-os.org/
With AI I feel like a lot of these bygone-era OS's could see a whole new ecosystem of modern apps within a very short period of time.
1. https://github.com/machiya-kobo/shiori/tree/main#haiku
At this point, they could likely decompile MacOS classic and rework it to give it modern memory protection, virtual memory, preemptive multitasking, and networking.
It does but not all that much.
I had a Classic II, so a very limited machine.
Not a "road apple" but a "compromised Mac":
https://lowendmac.com/1991/mac-classic-ii/
68030 on a 16-bit bus, max 10MB RAM, no expansion slots so nothing except SCSI.
So, I put 10MB in it, a bigger SCSI HDD, a SCSI Ethernet adaptor on the back, and built both OSes up from scratch.
MacOS 6.0.8 with all the extras: a menu bar clock, hierarchical Apple menu with modular Control Panel, MacTCP, etc.
And MacOS 7.6.1, which doesn't officially support the Classic II as it wants 12MB RAM minimum -- but I had RAMdoubler. OpenTalk, Netscape Navigator 3, Communicator 4, some early Internet Explorer, etc.
Honestly, there was little difference. It was usably quick on 7.6.1 and more stable. So many things that are extras on 6.0.8 are built in to 7.x that it doesn't need that much more disk or memory.
7.x did more, made it easier, and ran well.
But, as an example, on roughly 1MBs ADSL, it took about half an hour to render the top-left quarter of https://slashdot.org/.
Perfectly usable machine, could do email, FTP, Gopher, but forget it on the WWW on of the noughties (2000-2009).
Gopher://typed-hole.org it's fine too.
It's also available for both 68k and PPC architectures. And the PPC version can run 68k software (it internally emulates a 68020)
I've a wild whim to try this with Windows 95. What's an x11 or wayland? we're going EXPLORER.EXE!
Skins and theming only gets it so far, I want it to actually be the Win95 front end with Linux underpinnings.
It had most if not all of that.
It had networking from the start with AppleTalk, later Ethernet and internet with MacTCP.
MacOS 9 had a preemptively scheduled kernel.
The problem is having that and supporting the software ecosystem, which depended on cooperative scheduling without having memory protection.
MacOS 9 ‘solved’ that by running the classic OS in a single process. It had APIs for creating preemptively scheduled threads, but those threads were limited in what they could do.
You are describing attributes of the NeXT-based OS X but calling it MacOS 9.
MacOS 9 was the final version of Classic. No preemption, weak virtual memory, weak cooperative multitasking, no virtual machines for anything.
MacOS 9 is the OS that ran inside the Blue Box on Mac OS X for backwards compatibility.
You're mistaken.
> MacOS 9 [had] no preemption
Classic Mac OS has had vertical retrace (VBL) interrupts since System 1.0 (which are a form of preemption). But suppose we disregard that.
>> MacOS 9 had a preemptively scheduled kernel.
The GP is correct. Applications run cooperatively within the Blue task, but the Blue task itself runs preemptively with other MP tasks (which an application can create).
https://en.wikipedia.org/wiki/Mac_OS_nanokernel
https://en.wikipedia.org/wiki/Multiprocessing_Services
Very very little used it. About the only classic app I ever heard of that could even use pre-emption and background execution were some demanding Photoshop filters. Enough that Daystar Digital built multiprocessor Mac clones just for that alone:
https://lowendmac.com/1995/daystar-genesis-mp/
Within the MacOS kernel it is as coop as ever, and there were no different OSes inside virtual machines. No, Tenon MachTen does not count.
Haiku specifically does not accept AI-generated code.
I expect if you use AI to explain how to write it and then write it yourself that would be okay.
You need to be able to explain your work without just pasting in what Special Needs Wintermute says.
Haiku still doesn't boot on many modern systems.
Haiku can use all the help it can get.
You'd lose compatibility with the applications, though, so you'd have to decompile and rework those as well. And even if you did, you couldn't legally distribute any of it.
An alternative approach is high-level emulation. Running a separate instance per application gives you process isolation (via the host OS) for free.
> I assume booting an OS with a mere few megabytes of RAM footprint would only take milliseconds?
I haven't measured it as such, but yes.
I really need to dedicate some time to understand why. I'd love to contribute with apps and drivers.
The original Nike store in NYC purchased one to do their signage media playback. It didn’t go well.
Beyond that, I'm not sure if buying Be would have fixed the managerial problems at Apple. Would they have been able to add the required features to BeOS to turn it into a production OS without the project turning into another Copland? Would the existing Apple management have slimmed down the massive Apple product line that had dozens of nearly identical models? Would it have gotten rid of dead-end projects like Newton and Pippin? Etc.
Jobs is what makes or breaks Apple in that critical period. I didn't like him but that's relevant to the success of the company. JLG did not have whatever it was Jobs gave the company.
I wish that had happened... it might have saved both companies.
We paid Cygnus(?) millions for that. The multiple virtual inheritance needed for MediaKit was a real joy to get working.
32-bit Haiku can run old Be apps, but must be built with ancient GCC.
64-bit Haiku is built with modern GCC but it is not binary compatible with old BeOS.
This is a surprising amount of effort to not break compatibility ;-)
Which is what Windows has been doing since C++ replaced C for most of the systems programming stuff, around Vista timeframe.
Note that on Android they took an hammer solution, programming patters to invoke such code on main thread, have as outcome that there are either lint compile errors, or platform killing the application, for those flows not verifiable at compile time.
But it was 90s era C++, so probably that was all just a polite agreement and the reality was that circumventing the message passing to directly call methods on objects that belong to other threads was common, and just as likely to happen by accident as on purpose.
If not, desktop computing would be taken over by C++ as main systems programming language, and UNIX like computing relegated to servers.
In the places where there's something entirely different going on, such as networking in earlier BeOS, it's trash and you'd obviously want to throw it away and do what Unix did - Be were doing so. So a hypothetical turn of the century fruit-flavour BeOS is probably much closer to "Unix with a different UI" than you're thinking. NeXT changed nothing there.
The amount of work done by Haiku to provide a proper POSIX userspace support proves the point.
There were several companies that had the BeOS source and that source can be found in the wild. It is speculated that yellowTAB ZETA was based on unlicensed BeOS source code.
1. The Rhapsody developer previews, which are NeXTstep with a menu bar at the top and desktop icons, and a Platinum skin.
2. Mac OS X Server 1.x which has cascading finder windows, an icon view by default, and some other things much like that.
3. Mac OS X 10.0, which I used, or tried to use, as a daily driver, with a broadly Mac-like experience with an Apple menu, but with app names next to it containing global "about" and "quit" options, and so on.
It never did acquire any of the nice stuff that came in with System 7 (e.g. drag-and-drop customisable Apple menu stored in folders in the System Folder) or MacOS 8 (e.g. folder drawers that shrink to tabs).
Yeah, a lot of those “blue” features never were adopted or came back. The whole spatial Finder concept was lost.
https://www.youtube.com/@designedinca
(Specifically they talk about Be beginning: https://youtu.be/5IFxwnXASyQ)
Now imagine macOS progressing to the point where title bars have been replaced with toolbars, and buttons no longer have borders, so you have to guess what part of the window will drag it.
:-|
I remember using the fluxbox wm like this back on the university Sun machines
Granted it was already Windows 10, so nothing that original.
I loved the tabs on BeOS.
https://github.com/RamonUnch/AltSnap
https://github.com/stefansundin/altdrag
I was installing GNOME pieces compiling from source, on top of Sun Solaris. So it was a weird configuration. But FWIW I relied on the tabs a lot.
One of the few upgrade experiences that was a discernable improvement and completely revised experience.
And while I agree that Steve Jobs and Next were the right business (and people) choice, I still mourn the loss of a much better UI (never been a fan of the Mac UI, and it's my daily at-work system).
I wish that there was some edict from KDE Project management telling everyone working on the Plasma desktop to spend a week in Haiku or something.
The amount of indirect "open a dialog box, click 6 tabs down, then enter a value" stuff in KDE that is a single drag in Haiku drives me mad.
GNOME 3 was trying to built a clean modern minimalist desktop without all the clutter inherited from the design of Windows... But all they know is, very visibly, Windows and KDE.
RISC OS is that clean legacy free desktop. It's unlike anything else, built from scratch by a team not interested in what the rest of the world was doing.
And it's still alive and still updated and works well on modern hardware. Several separate efforts are building 64-bit replacements today.
https://www.riscosopen.org/content/
It runs on all Raspberry Pi models up to the 4, and runs really well. As of version 5.30 it supports the Wifi chip in the Pi so it can connect to WLANs.
The owners of the IP are RISC OS Developments Ltd (ROD) and they have an enhanced version -- free on the Pi -- called RISC OS Direct, with an IPv6 stack and a modern WebKit browser:
https://www.riscosdev.com/direct/
They also sell more capable hardware for it.
There is another fork of the OS that is still proprietary. That's owned by 3QD. They used to sell upgrades for real Acorn-compatible kit but there's none of that that isn't vintage now, so it focuses on a software emulation that runs on modern x86 machines:
http://www.virtualacorn.co.uk/index2.htm
https://www.theregister.com/software/2022/06/21/risc-os-is-3...
Search the Reg for "riscos" and you'll find interview with the original core team, looks at the last couple of FOSS releases, the Moonshot effort to go 64-bit and more.
I know almost nothing about it, so I will give your links a read.
The other thing is that it says right at the start of the BeOS Book - and this is carried across to Haiku - is that you shouldn't have a spinner or hourglass. It should do *something*, it shouldn't make you wait.