data1701d (He/Him)

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

- Lt. Cmdr Data, Star Trek: Generations

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

help-circle
    1. Alpine is still a Linux distro, just a lighter one. Also, busybox is a set of standard utilities as an alternative to coreutils; I have no idea how it’s particularly relevant here.
    2. The thing is, I’m not using only Docker. I also use native nginx as a reverse proxy, for which I like Debian’s defaults, as well as SyncThing, which are both well-maintained packages in Debian. Also I kind of prefer glibc distros. While glibc kind of sucks, so much stuff I like using prefers or requires it; for instance, last I saw, mDNS/Avahi resolution on BusyBox was kind of a pain in the rear.
    3. Most of what I use Flatpak for isn’t network-facing or opening unverified files anyway; the most important applications I do run the native Debian version. Honestly, truth be told, you are correct that I do often prefer native versions and will run the native Debian package if possible (and considering the current age of stable, a lot of them really aren’t that old; Inkscape is basically still the latest version, for instance, while Firefox is always kept to the latest ESR); at some point, though, I do find a Debian package that is too behind to do what I do (though rare, TBH), and despite some issues with Flatpak, at the end of the day, I need to just get a piece of software installed and get on with my day. In that case, I just do a Benjamin Sisko:

    Benjamin Sisko says “I can live with it”



  • Honestly, in the age of Flatpak and containerization (as well as Debian often being well-supported by upstream projects for script or package-based install), I feel like the age of Debian packages isn’t that annoying anymore; anything important gets security patches, and it’s easier than ever to use 3rd party software without breaking your system. I will add that Debian seems to be much better these days at making sure either a reasonably up-to-date version ships with a release (and can be kept secure during a stable cycle) or not shipping it at all as to allow the user to install it themselves.

    I remember back in just 2021 when it took months after Firefox ESR 78 went EOL for them to update Bullseye to 91; recently, it only took them a few days after 140’s EOL to switch to 153 (and 91-115 and 115-140 happened without much note either), which isn’t perfect, but much better than it was.

    If you need to install it on a new laptop, backports often has you covered. I ran a backports kernel for about a year on Debian Bookworm to get my laptop’s Wi-Fi modem working; I was able to quit using the backports kernel once Trixie came out.








  • I basically just gave three (or at least 2, as the DISCO one maybe is a bit iffy) examples of modern Star Trek scrutinizing the means despite the obstensibly good ends.

    Also, another example is S2 E2 “Ad Astra Per Aspera” borderline almost literally puts “the moral cost of the means” (keeping good genetically modified people like Una out of Starfleet) that is ostensibly done for the ends of preventing another Eugenics Wars. I wouldn’t hesitate to call this episode one of the best in the whole franchise, very much in the tradition of court case ethical discussion episodes like “Measure of a Man”.

    I don’t think one can make a blanket statement about newer Star Trek quitting “believing something”; sure, it may be uneven in quality (maybe more than classic)*, but dismissing all of “NuTrek” out of hand is akin to throwing the baby out with the bathwater.

    : I mean, there’s whatever DIS season 2 was, Section 31, most of PIC, etc., but also, it’s not like good swathes of classic Trek aren’t also kind of crap - I mean, there’s the time Riker murdered his clone and nobody batted an eye, as well as TOS S3, TNG S1, and the inconsistency of VOY. Even in the good classic episodes, it’s not like every one is “do the ends justify the means” - in addition to other ethical themes, classic Trek still had room for simply "Cool sci-fi s** happened and we have to deal with it", not to mention episodes focused on interpersonal drama like “Data’s Day” or any of Deanna’s “Oh f*** my mother is on board” episodes.


  • I would say it depends.

    I mean, the ends not justifying the means is kind of the entire point of DISCO S1 (whether or not the rest of DISCO embodied it is a different matter); Burnham has to let go of what Lorca summarizes as “Universal law is for lackeys. Context is for kings.” or in other words, the ends often justify the means.

    Also, SNW is better about it, than say, PIC; for instance, SNW S3 E7 “What is Starfleet?” from 2025, for all its flaws (including in some ways being very similar to TNG “Tin Man”), basically has the crew going “WTF! The ends (saving an alien race from a war they didn’t start) do not justify the means (enslaving a sentient space whale)!” Also, SNW 1x06 is basically “ends don’t justify means”, although mostly because it basically copied “The Ones Who Walk Away From Omelas”.


  • XFCE!

    Donkey from Shrek

    In all serious, while I use XFCE on most personal things, if I was pressed to choose between the big two, I think I’d choose KDE over GNOME; in fact, when I had to loan my younger sibling a laptop recently and that laptop was too old to run Windows 11, I put them on Debian with KDE. I think KDE is also my backup plan if major applications start dropping xorg support before XFCE has implemented sufficient Wayland support, although they seem to be making progress.

    Out of the box, KDE tends to be more Windows-like and just better for my workflow in general, while GNOME can just be… weird. Like, I don’t quite hate GNOME as much as I used to - I plan on throwing it on an old Surface tablet soon - but like others have said, it’s very opinionated and doesn’t like customization and whatnot. I also resent GNOME in the sense that they tend to make design designs (such as in GTK 4) that reduce ease of interoperability across different open source desktops.








  • True. At my tech helpdesk, I’ve seen people who keep their Macs on very old versions even if their hardware supports much newer (and non-Tahoe) versions and suffer problems because of it.

    For instance, the other day, a woman’s Microsoft Office quit working because she was still on Ventura, which no longer gets security updates. This was on what I believe was a 2022 Macbook.

    I think something is seriously wrong with Apple’s update system. I mean, the Windows approach is objectively wrong, but automatic update systems need to be at least a bit aggressive.