But did it support RGB?
Didn’t think so, checkmate!
Comment on The driver for my mouse occupies over 1 gb
HugeNerd@lemmy.ca 1 day ago
The mouse driver used with the Commodore 64’s GEOS operating system uses 3 blocks on disk, less than a kilobyte.
But did it support RGB?
Didn’t think so, checkmate!
A lot of fancy early RGB mouse came with a companion app that needed 10MB at most, and that was ridiculed.
That driver was using 0.5% of system resources! I thought it would be worse when I saw "259 blocks free", but overall that's pretty good.
Well that’s just a screen shot of the directory listing of the GEOS disk from the 64’s default “OS”, the BASIC interpreter. That 3 block file also contains information that only GEOS sees, the actual executable 6502 code is likely in the 500 bytes, if that. The user manual for the mouse actually contains an assembler listing of the driver. It ain’t big.
The 64, of course, was never designed with a mouse in mind, so Commodore engineers used the analog paddle inputs to encode the mouse XY motion. So the “driver” really just reads the A/D converters for the paddles and fudges some kind of motion information out of it.
It works quite well. The 64 only has a 320x200 display, so it’s not like you need a gaming 1000DPI 1ms mouse.
ZILtoid1991@lemmy.world 1 day ago
Most of the reason why the Logitech driver is so gargantuan is a separate Chromium browser instance, because someone thought that apps should be all websites first, which lead to most GUI libraries being developed for javascript and most devs being taught to be web developers.
merdaverse@lemmy.zip 1 day ago
VSCode is also electron with a 100mb download size and 400mb install size. I think it has 1000x more functionality than some shit Logitech UI where you change LED colors. This sounds more like incompetence on the Logitech team than a problem with electron itself.
Aceticon@lemmy.dbzer0.com 1 day ago
Or you can use qbittorrent-nox and just interact with it via its the web interface.
ZILtoid1991@lemmy.world 1 day ago
The 1gb of KDE dependencies are one time only, but there’s also the option of just using OpenGL + bare x11 or Wayland for GUI. If my game engine could pull it off, if IMGUI apps could pull it off, then everyone could pull it off, we just need a UI framework not ddependent on either GTK or qt.
merdaverse@lemmy.zip 1 day ago
“One time only”? In theory yes, in practice I don’t have anything else that needs those KDE dependencies. When I remove qbittorrent I can safely remove them. This is just a reality check that desktop GUI frameworks and package management are really not much better than Electron/html as lots of comments in this thread seem to suggest.