Post B6Be9S7W0M5xvk5ahk by andrewg@mastodon.ie
 (DIR) More posts by andrewg@mastodon.ie
 (DIR) Post #B6Be9S7W0M5xvk5ahk by andrewg@mastodon.ie
       0 likes, 1 repeats
       
       RE: https://toot.cafe/@baldur/116555400927893426I’m constantly amazed that in 2026, “lag when typing” is a thing. I remember in *1992*, on a DEC3100 workstation, that keyboard and mouse lag simply did not happen. Right up until your system crashed from OOM, and sometimes even *afterwards*, the mouse pointer carried on as if nothing was amiss.We have sacrificed everything on the altar of DX.RT: https://toot.cafe/users/baldur/statuses/116555400927893426
       
 (DIR) Post #B6BeD8aoY70OWdYD1k by liw@toot.liw.fi
       1 likes, 0 repeats
       
       @andrewg Back in the 1980s, I used QEdit, which had direct access to graphics card frame buffer, in text mode. To write a character you update a byte in memory. It was so fast it's unbelievable today.Today, I have a multiuser  graphical desktop. Many orders of magnitude more complicated, and some of that is for good reason. I would hate for my text editor (or any random software) to have direct write access to the frame buffer.But there is lag. Noticeable lag. Would be nice not.