Hacker News Reader

Comment by swerner | Hacker News Reader

Linux 20 years ago wasn’t what it is today. Low latency audio for example, that was something that BeOS in the late 90s could do out of the box, a similar experience on Linux required special kernel patches and some compromises or it simply wasn’t there at all.

Audio latencies of less than 10ms on consumer hardware were otherwise unheard of. Windows, out of the box, was still operating in the 100+ms range.

View on HN

Yet after 20 years of Linux distros, we still see Linux struggling with getting a simple desktop together without X or Wayland crashing itself and logging you out because of someone wanting to tweak their desktop via a custom init script or systemd script.

Let me know when I can support 100% of all Linux distros and users like I can with macOS and Windows.

There's only one macOS and only one Windows. You can support only the big distros (basically Debian/Ubuntu or/and Fedora/openSUSE; for example that's what Chrome does) and let respective distro maintainers handle issues to other ones. Or just use Snap or/and Flatpak.

I would love to see a BeOS/Haiku userland on top, of the Linux Kernel. That would bring wide hardware support, including HW accelerated 3D (something BeOS was always lacking). It is not going to happen though, the attempts that were didn’t go far and porting the entirety of Haiku would be a gigantic effort that no one is volunteering for.

IIRC that was one of the two/three main ways forward discussed and planned for after Be Inc went belly up.

- OpenBeOS (Haiku) - rewrite from scratch

- Option 2 (can't remember if it had a name) - was just to Implement BeOS userland on a Linux, to get free access to drivers etc. Most of the Be community was not interested, and I cannot remember if they even got started..?

- (YellowTab - Some company had access to BeOS sources and started releasing and somewhat updating the OS on a commercial basis - but don't think they actually had the rights to do that....)

If only Apple had chosen to go for BeOS X over NeXT.

This would probably have meant that the Mac wouldn't have become so popular amongst developers. At least that was the reason for me to switch to Mac because it's a "proper" UNIX with a window system that actually works ("Linux on the desktop" has mostly caught up in the meantime, but 10 years ago that was quite different).

Haiku has a perfectly good POSIX layer; I expect it would have been fine.

BeOS was less compatible. There were also many improvements to it in the later versions. When NeXT bought Apple[0], BeOS was not even in its pre-release phase. Its heyday, such as it were, was really on Intel, with R5 and the Personal Edition, in the last few years of the 90's.

[0] For -$400M :)

Option 2 : BlueEyedOS / Cosmoe

Yes! That was it.

When on the subject of "things lost in the mists of time", did the original OpenBeOS lead (Michael?) ever return?

I would love to see a hardware company pick up Haiku and “do an Apple”: make a small set of focused computers with excellent support for a specified set of hardware.

Intel should do this. It's rounding error and they can use it to push the envelope. Intel should have done this with Linux, Solaris, Beos years ago to push Microsoft.

They won't.

Android, not joking, most of the original team are former BeOS engineers.

And it's still terrible at low-latency response compared w/ iOS...

That has been sorted out, but you need to make use of NDK APIs like AAudio, and naturally own a flagship device, so are the Google ways.

The NDK wouldn't be a problem, but requiring powerful devices speaks volumes about how lacking is Android in that field, when one can build low latency synthesizers and effects using a cheap old Raspberry PI 3. https://www.youtube.com/watch?v=YtU8jMtbplE

Yeah, but that isn't running a managed runtime on top, and all the security knobs turned on to mitigate classical C and C++ CVEs.

Most maker audio devices are making use of bare metal with Cortex and ESP32 chips, if the ultimate performance on the cheap is the goal.

True low-latency workloads on modern Linux (and 10ms is definitely low-latency!) still require a custom patchset (namely PREEMPT_RT). It's slowly making its way through the process of being upstreamed, but still.

I'm glad you mention audio because I'm going to spend 60€ on a dedicated microphone just because Linux cannot use simultaneously my Bluetooth headphones and their integrated mic without manually changing the codec (which additionally sucks when using the mic). Some problems improve but others simply never dissapear, like audio. Maybe there is a lack of interest or maybe is a design or a process problem, I don't know.

Reply on news.ycombinator.com