Re:Why does the Commodore C128 perform poorly when running C...
by actionfromafar on Friday December 09, 2022 @04:05PM
(#33926449)
I think people would have sat up and noticed if they took away the real-time aspects of the platform. On paper, there isn't much about Amiga which was real-time. Culturally though, so many programs were realtime. I still miss the instant latency. iOS, Android, MacOS etc nothing holds a candle to how it felt.
[ Parent
| on HN ]
Re:Why does the Commodore C128 perform poorly when running C...
by robinsonb5 on Friday December 09, 2022 @04:30PM
(#33926657)
This. There were plenty of flaws in the Amiga experience (like "please insert disk..." dialogs that simply won't take no for an answer because the programmer didn't check for errors) but that instant feedback is what's missing from so many modern systems. I call it "having the computer's full attention" - and it comes from the fact that (using the stock GUI system) the gadgets which make up the UI are drawn and redrawn in response to input events on the "intuition" task rather than whenever the application's main loop next gets around to it.
That's why Magic User Interface felt "wrong" on the Amiga, despite being a superb toolkit in lots of ways* - drawing was relegated to the application's task, making it feel "Windowsey".
(*I would genuinely like to see a port of MUI to X / Linux.)
Re:Why does the Commodore C128 perform poorly when running C...
by rep_lodsb on Friday December 09, 2022 @06:01PM
(#33927590)
Because iOS, Android and MacOS are all based on a 1970s minicomputer operating system designed to communicate with ASR33 teletypes, with layers and layers of bloat added on to it over the years.
That it can support a graphical user interface at all is only due to having a lot of CPU time to waste!