3 ms·
I'm not missing the point. I want lightning fast response from software to my actions. If there is one thing I cannot stand, it's when the input loop loses even
by Annatar 8y ago
I'm not missing the point. I want lightning fast response from software to my actions. If there is one thing I cannot stand, it's when the input loop loses events, which happens very often on Windows and my Linux powered TV. I want to throw them both out of the window, it drives me insane.
- Baeocystin 8y agoI miss the instant-on, straight-to-REPL, ~1 second reset features of my old Commodore 128. And I am not kidding in the least when I say that. Regarding more modern operating systems, BeOS was so nice to use. Here was an OS that had UI/single-user needs baked in to it from the beginning, and it was a breath of fresh air. I'd liken it to the experience I had switching from a 60Hz monitor to a 164Hz one- I didn't really think about it much at the time, other than I wanted a gsync-capable display, and one was one sale. But the smoothness of the scrolling, mouse use, etc was so much more pleasant. And yet I never would have complained about the 60Hz screen until shown the alternative. Venturing in to personal opinion, I'd also say BeOS was developed at the inflection point between engineering running the show, UI be damned, and where we are now, with designers running the show, actual capability be damned. It was a good mix.
- Annatar 8y ago"I miss the instant-on, straight-to-REPL, ~1 second reset features of my old Commodore 128." As a C=128D owner, I hear you loud and clear. It's a slap to the contemporary programmers' faces that a 1 MHz MOS 6510 based system was more responsive than multicore GHz, hardware accelerated systems we have now.