• 0 Posts
  • 14 Comments
Joined 1 year ago
cake
Cake day: July 29th, 2023

help-circle


  • I’ve been using Dvorak since the late 90’s. When I type on a qwerty keyboard, it feels like my fingers have to fly all over the place to hit all the keys.

    With that said, Dvorak has a few gremlins. The most annoying are the y/f keys where I have to shift my hands slightly to hit those keys. The copy/paste ctrl-c and ctrl-v keyboard shortcuts are also a lot less convenient but I just deal with it. It’s also annoying having to rebind keys in pretty much every keyboard-heavy game.

    I’ve never really thought of Colemak as a big enough improvement over Dvorak to relearn how to type on that layout, though if you’re looking to switch from qwerty it may be worth considering. The Workman layout seems interesting.


  • I can see it. My corporate work laptop is locked down with their security and monitoring software, so I’m not using it for personal things, even if it is allowed for some limited things. And there’s company resources that I can only access through the machines under their control, so I couldn’t ditch it either. And using that laptop for a second job would be a big no-no.

    I can see the school laptop being similar, though my experience is that they tend to not be locked down quite as hard as the corporate machine, unless you do boneheaded things with it and piss off the school’s IT department.

    So I can see the need for a personal computer, plus it’s always nice to keep that well separated to avoid things like incidents hooked up to a projector and screen sharing.




  • The games that are going to be the hardest to preserve may end up being many of the mobile games that are popular now.

    These games are usually installed through an app store, so if the app store pulls it, that could be it for new installations of the game unless the game can be extracted off an existing device. And even if you manage to extract the game off of a device, in order to get it onto another mobile device will likely require some way to side load it.

    Many of these games also depend on a server so once the server is turned off that’s another way the game to die.

    The mobile devices these games run on aren’t built for the long term either. They are essentially disposable devices meant to last a few years and then be tossed. They aren’t built to be serviced or repaired. Eventually the batteries will die, and while you can replace the battery, there’s no standardization of battery packs and eventually replacement batteries won’t be available either.

    Even if you can get an old mobile device going, there’s no guarantee that you’ll actually be able to do anything with it, because the device itself may depend on some remote server just to function that could someday be shut off. There’s already old phones today that if you factory reset them, it effectively bricks them since they need to contact some activation server as part of the initial setup process and that server is long gone.

    Of course, many people may ask - who cares? Perhaps so, but I’d bet a lot of people said the same thing about the old Atari and Nintendo and Sega and MS-DOS games that were popular years ago and are still popular today.

    It’s kind of interesting that pretty much all the games I played as a kid are still accessible to me today - in many cases the original game is still playable on the original, still functional, hardware. But a lot of kids today growing up today playing mobile games on a phone or a tablet, when they are my age, could very well have no way to ever experience those games again that they grew up with as kids.





  • Not too long ago, on a Slackware box I needed to manually change glibc to another version. No problem, I thought, just remove the version that’s there and install the package for the version I needed. So removepkg glibc and then immediately dawned on me… oh wait I really didn’t want to do that… Of course, after that installpkg and pretty much everything else was broken since pretty much everything either depends on glibc, or has a dependency that depends on glibc, so I couldn’t install the new package or do pretty much anything other than smack my forehead.

    Wasn’t actually too big of a deal to fix. Used another computer to create a bootable USB stick with the Slackware installer, booted the computer with the USB stick, and did some chroot trickery to reinstall the old glibc package again. Then booted it back up normally and used upgradepkg to change glibc like I should have in the first place.



  • I did the opposite. After one of the big updates, Windows 10 decided it was no longer going to work with the Vista-era drivers for an old Core 2 Duo laptop. To be fair to Microsoft, was I pretty impressed when I initially installed Windows 10 and it accepted those ancient drivers without any complaints on a laptop that was 10 years old at that time.

    So I instead installed Manjaro and everything worked just fine.