4 ms·

I remember back in the Amiga days, the processes for the GUI would be totally separate from the program logic. Add the pre-emptive multitasking and you would ha

I remember back in the Amiga days, the processes for the GUI would be totally separate from the program logic. Add the pre-emptive multitasking and you would have GUI elements that would respond instantly always, even when the rest of your program was hung! Of course, the button callbacks wouldn't fire, but the button would appear to press, you could move windows, etc. Did a lot to reduce the perception of lag, whilst obviously introducing quite a few quirks of its own.

renox 8y ago
The Amiga didn't have multiple address space so that's cheating.. I've never used an Amiga but BeOS was really much more responsive than either Linux or Windows but that was before SSD and multiple cores were available so maybe now the difference would be much less noticeable.. There is Haiku (in alpha or beta) but AFAIK it hasn't any native modern web browser..
- waddlesplash 8y ago
  Depends on what you mean by "modern", I guess? https://www.haiku-os.org/files/get-haiku/webkit.png https://www.haiku-os.org/files/get-haiku/webkit.png
  - renox 8y ago
    WebKit is modern yes but it isn't really "BeOS native"
    - waddlesplash 8y ago
      It uses native APIs for drawing, text layout, media playback, and HTTP. I don't know how much more native you want...
      - renox 8y ago
        WebKit wasn't designed for BeOS so I'm not sure that using native API to draw is enough to make it a real native BeOS..