• 10 Posts
  • 16 Comments
Joined 11 months ago
cake
Cake day: August 9th, 2023

help-circle










  • This may have been true historically but I’m not sure it still holds up. I switched to Linux Mint as my regular OS a while back and the only driver issue I’ve had was that the installer didnt properly install my wifi card’s proprietary driver (which was working during live boot from usb), so I had to tether to my phone to download the driver through the driver manager. It even installed Nvidia drivers just fine.

    It might still be an issue for more barebones or heavily customisable systems but I’m fairly certain nobody’s recommending people switch to Arch for their first Linux experience.



  • A keyboard without tactile feedback is objectively worse than a keyboard with tactile feedback, excluding other factors.

    I’ve never had a physical keyboard lag out then send an entirely different keystroke because it thought I held a button, or send a single keystroke because I was typing too quickly.

    I’ve never had to wait a moment for a physical keyboard to show up after selecting a text box.

    I’ve never had the entire layout of a page shift to make room for a physical keyboard whenever I select or deselect a text box.

    I’ve never had a physical keyboard prevent me from using the number pad and force me to use the full keyboard (or worse, vice versa) because of an improperly configured input box.

    The way I see it there are exactly two real benefits to integrating a software keyboard into a touchscreen: reduced physical complexity (the entire device is essentially just one screen), and easier access to emoji. A touchscreen keyboard performs far worse as a keyboard. It’s a valid trade-off for a small mobile device, but it’s not objectively better.


  • That reminds me of an issue I had when I was installing Mint. I tried out a live boot first and everything seemed to work except there was no internet connection. Turns out my WiFi card needs a proprietary driver, but no big deal it installed easily enough just from the boot disk. Internet’s working, all looks good, so I go ahead and install Mint proper, remove the live boot usb, start the system, and savour that new Minty smell. But hang on, there’s no WiFi, I forgot to install the driver! Should be an easy enough fix though, it wasn’t hard last time.

    So I go to install the driver and the first thing it says is that it needs the boot disk to get the driver. That makes total sense, can’t install something you don’t have! I plug in the usb again and now it should all be plain sailing, after all it’s just installing a driver that worked 20 minutes ago, right? Sadly no, that would be too easy; for some reason now it’s missing dependencies! Or something along those lines anyway, I forget exactly. But can’t it just install those from the boot disk? Well apparently not, it instead tries to connect to the internet to download them. This obviously fails since I don’t have a WiFi connection, which is why I’m installing the driver in the first place. All I get is a popup saying it can’t install some stuff because there’s no internet connection, fix that to get your internet connection. This is the point where face meets palm. I’m sure there’s some fiddly “proper” way to work around that but the thing is I’m incredibly lazy so I’ll just take the quick option instead. I plug in my phone and use a tethered connection. I run the install again and it finally goes through, at last the system is ready to use! It’s been mostly smooth sailing since then (though I did get annoyed enough at NTFS a couple of months ago that I just reformatted a data drive and wiped a ton of data I probably didn’t need).

    Tl;dr: I had to tether to my phone for a minute. Traumatising!