4 ms·
I remember many years ago, when a 16 MHz 68030 Macintosh was somewhat usable, but old and slow, by the standards of the day. I had read how, when the 68000 cam
by perl4ever 7y ago
I remember many years ago, when a 16 MHz 68030 Macintosh was somewhat usable, but old and slow, by the standards of the day.
I had read how, when the 68000 came out originally, it was considered to be a "minicomputer on a chip", while the 68030 was anticipated to be a "mainframe on a chip".
So, I was unable to viscerally appreciate that perspective, until I ran the original MacPaint, which was extremely optimized for the 8MHz 68000 in the original Mac, and then I was amazed at how fast the 68030 was.
- NeedMoreTea 7y agoHah, I can mention latency again! I had the Amiga, 68000 at 7.09 MHz (PAL, NTSC ran a teeny bit faster). Both Mac and Amiga gave fully featured, incredibly low latency GUIs. They might think a bit after the click, but compared to a modern GUI, oh so snappy. Windows, OSX, X with whatever Windowing never get close to that instant tip of your fingers response. I miss low latency responses.
- perl4ever 7y agoWell, I wouldn't make such a categorical statement about latency. I remember an early Amiga word processor that had an unbelievably laggy and slow UI, such that it was basically unusable. The Mac mouse pointer was always responsive due to interrupts, but that didn't mean that what you clicked on was. However, the thing that I hate most about the modern web and similar UIs is that they reflow or otherwise move the content you are looking at after you click and before the click is mapped to an element, so you don't get what you click or tap on. This is absolutely unforgivable in my opinion, and absolutely not a matter of degree or grey areas unlike most of the things people complain about.
- NeedMoreTea 7y agoAmiga's pointer was a hardware sprite, so that always stayed responsive. Was more thinking of the OS's themselves rather than within applications. You could certainly get Amiga to slow down in the apps, particularly if you were programming it badly. As it generally only redrew when needed and managed layers and viewports pretty well, getting it that laggy would have taken effort. :) Took years after I abandoned the platform for serious use for Windows not to always be more sluggish, and get dramatically worse when under load. Course by then I was on '040 comparing with Pentium something.
- mixmastamyk 7y agoDefinitely could be poorly written exceptions. There is a good post here describing keyboard latency on old computers. https://danluu.com/keyboard-latency/ https://danluu.com/keyboard-latency/
- dreamcompiler 7y agoThis is especially egregious on mobile because it's much harder to point at anything accurately with your finger.