data1701d (He/Him)

“Life forms. You precious little lifeforms. You tiny little lifeforms. Where are you?”

- Lt. Cmdr Data, Star Trek: Generations

  • 9 Posts
  • 417 Comments
Joined 2 years ago
cake
Cake day: March 7th, 2024

help-circle


  • May I ask: when did you last try Firefox? There was a period during the 2010s when it has truly horrible performance, but they rolled out some major updates several years ago that greatly improved performance (though wouldn’t call some of the UI changes improvements).

    Honestly, every major rendering engine is terrible in some way.

    • Blink is resource intensive and has so many non-standard APIs for the sake of Google’s version of “Embrace, Extend, Extinguish”.
    • WebKit takes 50 years to support the newest standards.
    • Gecko (Firefox) is non-modular and is limited to being used in Firefox, Thunderbird, and forks and Firefox as a result. Its performance is also somewhat worse than Chrome’s, but not noticeable for daily use.

    Ultimately, I choose Firefox because its issues are the least annoying to me. I do wish its structure was more community-based and less corporation-eating-its-own-hand, but whatever. So long as Debian sees it fit to keep in its repos, I’ll use it.






  • External drives? Usually on most distros and file managers, it’s just one click.

    I have had a bit of a horrid time with Bluetooth, though, especially when it comes to audio. However, I will say Linux allows you to do some nuts things with Bluetooth like emulate a Nintendo Switch controller with NXBT, allowing you to use a PlayStation controller on a Switch with a spare laptop.

    As for audio, I feel like life has gotten much better for the layman since Pipewire.

    I don’t think VR setups are that common, and the Venn diagram of VR owners and Linux users has to be even smaller. I’ve probably only known 2 people who actually own a headset, and both of them were standalone Oculus affairs.

    Overall, I feel like it’s possible to conceptually understand Linux and which config file is while, while Windows registry is an incomprehensible beast. Also, it feels like Linux tends to have better errors that correlate to a specific problem, whereas the same Windows error could be caused by many different things and lead you on a wild goose chase through forum posts filled with generic advice and dead ends.



  • Debian Stable. Get it installed, get everything working right and configured the way this person likes it on a reasonable DE with default themes, and more likely than not, you won’t have to touch this thing for years.

    The setup’s not necessarily for noobs, but if you’re the one doing the setup, you should be able to get it into a place where it will pretty much never break for them.

    You should probably give them KDE or GNOME (probably KDE, as it’s more Windows-like and less my way or the highway than Gnome). As much as I love XFCE, it’s probably a good idea to give a layman a feature-heavy DE so that nothing is likely to be missing; also, it’s way too easy to accidentally delete panel items or entire panels on accident and a little annoying to restore things back to the way they were. KDE’s panels implementation mitigates these issues.






  • AMD GPUs are officially supported in the Linux kernel and Mesa. They pretty much just work out of the box with minimal setup on a fresh distro install.

    NVidia GPUs often require out-of-tree proprietary drivers to work with full performance; these drivers are often a pain to install and update. Supposedly, things are getting less terrible now, but NVidia is still overall more likely to cause you pain than AMD.

    Intel Arc dGPUs, like AMD, have decent native kernel and Mesa support from what I can tell, but tend to have worse performance than AMD. However, I hear they’re ridiculously good for video encoding!