6 ms·
This is one of the things I still miss about BeOS. On late 90s hardware, the OS wasn't quite hard real-time like QNX but the worst-latency latency was much bett
by acdha 6y ago
This is one of the things I still miss about BeOS. On late 90s hardware, the OS wasn't quite hard real-time like QNX but the worst-latency latency was much better than Windows 10 or MacOS on the latest hardware, even in the presence of heavy resource contention — I remember simultaneously surfing the web, downloading video from a camcorder with a Firewire interface which did not buffer, and compiling Mozilla. The UI latency didn't change at all, and the DV transfer didn't drop a packet — everything else got throttled back as necessary, of course, but that meant that, say, GCC took longer to run rather than impacting what I was doing in the foreground.
- outworlder 6y ago> I remember simultaneously surfing the web, downloading video from a camcorder with a Firewire interface which did not buffer, and compiling Mozilla Did you forget to run the OpenGL teapot? BeOS was magical. I wish I could use Haiku in my desktop today.
- jeffbee 6y agoIt wasn't magic, it just starved everything else whenever you waved the mouse around. In this respect it was no different from Mac System 7, even though the design wasn't the same.
- Gracana 6y agoThat's not true, classic Mac OS used a cooperative multitasking model, where processes had to be friendly enough to yield control back to the system / other processes to allow them to do work. A poorly programmed or greedy process could easily hog the CPU.
- jeffbee 6y agoSystem 7 checked for mouse motion every fraction of a second and if the mouse was moving it would drop everything and draw. It didn't need apps to yield for this to happen.
- anthk 6y agoAre you comparing that shit when you pulled down a menu in System 7 could bring a whole network down, with Be? Such as a good joke...
- anthk 6y agoThe CPU and the whole net by holding a menu item down.
- Retric 6y agoThat was arguably an application specific issue, though the OS was painful to code for. I actually coded some classic Mac OS networking code and it was insanely easy to mess things up, but eventually it ended up being rock solid. The trick was all level interrupts where supposed to only do almost nothing. You couldn’t allocate memory for example which was a major hint of just how minimal those functions needed to be. Worse with cooperative multitasking any running application could mess things up.
- anthk 6y agoThen do not talk about Classic Mac as something magical because compared to Be they were utterly ridiculous. For its era, System 7 was good, but later, it was worse than even Windows 98. Be tried to do things right, it was ~1995 after all.
- agumonkey 6y agoI see where java gui coder took their inspiration from /s
- flohofwoe 6y agoAnd that's exactly how a desktop operation system should behave. The most important priority of a user-facing OS should be the user after all.
- max38 6y agoAmen
- k__ 6y agoIs it possible to do this with Linux? Giving the UI very high priority etc.
- mmm_grayons 6y agoYes, with the RT-Preempt: https://wiki.archlinux.org/index.php/Realtime_kernel_patchset https://wiki.archlinux.org/index.php/Realtime_kernel_patchse...
- acdha 6y agoIt’s been a while since I tested it (pre-Wayland). The main problems I saw back then was that the window managers tended to do lots of file I/O for things like moving windows or opening menus so it was critical to tune the I/O scheduler (and NFS home directories were game over), and since rendering was up to the app it was common to have, say, the chrome respond relatively well but everything inside the window would be chunky on the main thread. I’d hope this is much better now given things like Wayland and the increased use of parallelism.
- marcosdumay 6y agoLinux used to do that out of the box. But there was a series of "quasi-real time has too much maintenance costs", "quasi-real time isn't even real enough for the real gains", and "our computers are fast now, we don't have to trade so much throughput for latency" decisions that were all very sensible but let us here.
- mensetmanusman 6y agoMy 5 year old uses our first iPad which is over 10 years old now. The keyboard UI from then is still faster than my iPad pro keyboard UI because Steve Jobs valued the priority of that in the stack :)
- bangonkeyboard 6y agoThey also ran surprisingly long, particularly the die-shrunk iPad 2: https://i.imgur.com/ELyFwFu.png https://i.imgur.com/ELyFwFu.png
- branko_d 6y agoI remember that about Amiga. Everything was just smooth. I still have fond memories of Cygnus editor being super-responsive to anything I could throw at it, even with SAS C running in the background. I was taken aback by how slow Windows 95 felt after I finally jumped the wagon and retired my beloved Amiga in favor of a PC, circa 1995. Just moving the cursor was incredibly jerky in comparison and things would randomly freeze for seconds for no apparent reason. Windows NT 4 was much smoother though. Even today, in Visual Studio, I regularly have multi-second pauses between a key press and the character showing-up on the screen, though this probably has more to do with Resharper than either Visual Studio or Windows.
- ygra 6y ago> and the DV transfer didn't drop a packet Considering how FireWire worked in comparison to USB that's not particularly surprising. The host machine was more or less out of the way while the FW interfaces did their thing instead of requiring constant hand-holding.
- acdha 6y agoKind of: it used DMA, but the buffer size wasn’t infinite. At the time, Windows 9x and Mac OS would lose data if you ran anything demanding. Windows NT and Linux might, depending on drivers and the exact nature of the other process’ activity.
- runjake 6y ago> but the worst-latency latency was much better than Windows 10 or MacOS on the latest hardware Citation needed. Do you have any numbers on that? I'm skeptical that BeOS has better latency than modern OSes on modern hardware.