• 3 Posts
  • 94 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle
  • Discussion: you can have an “extinction event” in any ecosystem-- not just biological ones.

    For example, the abandonment of steam locomotives in the mid-20th-century, or the Home Computer crash of the 1980s.

    Similar to a biological mass extinction, you have:

    • A discernable ecosystem change, either a sudden event (the introduction of reliable, mass-produced diesel locomotives), or a measurable decline of “habitability factors” (as hundreds of firms brought cheap 8-bit computers to market, retail space and overall consumer interest saturated)
    • a rapid diversification of new and exotic types to fill the vacated niches (the cabless “B-unit” and flexible “road-switcher” locomotive types didn’t exist in the steam era. The post-crash computer market brought in new entrants like cheap IBM clones, the C128 and Atari 130XE, all chasing a sub-$1000 market that was now free of Sinclair, Coleco, and Texas Instruments)
    • followed by a shake out and consolidation of the survivors/winners as they select for fitness in the new world (ALCO was a strong #2 in the diesel locomotive market in 1950, but didn’t make it to 1970. The C128 never became the world-beater its predecessor did.)
    • a few niches largely untouched (China was still building steam locomotives into the 1990s. The Apple II series lasted about as long.)

  • I always figured BSD should lean into the daemon imagery with a full heavy-metal branding: a suite of wallpapers with decidedly less cuddly daemons, a succubus OS-tan character… make it the go-to Edgelord Desktop.

    Then FreeBSD introduced that stupid sphere logo. No sense of branding. :P



  • I guess the assumption is more that for me, a fresh install is often about decluttering as much as anything-- the five Wayland compositors, three music players, and six pseudo-IDEs I tried and didn’t like don’t need to follow me to the next build.

    In a conventional install, that just means “don’t check the checkbox in the installer next time”. In a Nix-style system, this is a conscious process of actively deciding to remove things from the stored configuration, no?

    I suppose the closest I’ve gotten was recently migrating my setup from a desktop to a new laptop. Mostly copying over some config from my home directory, but even then, I wanted enough different stuff-- removing tools I don’t use on the laptop, adding things like battery monitoring and Wi-Fi control-- that it involved some reconfiguration.


  • I suspect the tooling isn’t quite there yet for desktop use cases.

    If I were to try to replicate my current desktop in an immutable model, it would involve a lot of manual labour in scripting or checkpointing every time I installed or configured something, to save a few hours of labour in 2 years time when I get a new drive or do a full install.

    The case is easier for defined workload servers and dev environments that are regularly spun up fresh.






  • Back in the Windows 8 era, I bought a little 8" tablet PC from Dell. It was flaky from basically day 1, and after ~2 weeks it bricked entirely.

    I go to RMA and they ask “If we refund you $50, would you be willing to keep the unit? How about $75?”

    Admittedly, they did give me a refund, but that was so the wrong branch to follow on the chat script, honey. If I’m going to be out over three hundred dollars for a paperweight it better at least be made of something cool like meteorite.



  • I started with some UMSDOS-based “full X11 desktop in 5 floppies” distro on a 486, then went through Slackware, RedHat 5 with glibc breakage, actually bought a SuSE boxed set in the 7.x era, mostly stuck with Slackware unril I realized I wanted stuff like Steam and perhaps some degree of dependency resolution is nice. Bounced off of Arch (the AUR is a terrible concept IMO) and ended up on Void, which gives me Slackware-like vibes, but a little more built for broadband instead of CD images. Been trying Debian Sid latrly, just because I put it on my new laptop and I figured I’d go consistent, but I’m not sure I’m sold. Everything works, but even for an “unstable”, the packages are dated and I dislike systemd on principle.




  • GNOME always seemed to be a solution chasing a problem, particularly once the licensing fears for Qt/KDE were settled.

    But now it’s one of the things Red Hat seems to impose on the world. Feels like everything controversial comes out of them or Canonical. I guess they have the commercial cash to prop up things like GNOME and Wayland and systemd and snaps until they gain traction, while more community-focused products can’t break the world for no reason.


  • I sort of liked GTK back in the day when it was still the Gimp Tool Kit first and foremost. When it was 1999 and your other choices were a broken Lesstif, an early C++ centric Qt, clumsy Tk, and pre-Cambrian Xaw, it was nice to have something full-featured and tasteful.

    Now I hesitate to pull in a GTK app because it won’t theme right (I want to use the same bitmap fonts I liked in 1999, but apparently Pango stopped supporting them) and runs the risk of convincing the package manager to dump several gigs of GNOME crud on my drive.

    I gather even the GIMP itself no longer tracks current GTK-- it’s become solely in service to GNOME and their absurd UI whims (* * * * client side decorations)




  • I’d love to know what the domestic spin is on this.

    What specifics is he promising this will deliver domestically? I can’t imagine Buenos Aires is on Putin’s shortlist even without the threst of NATO, and it’s not like Americans are goung to start beating the doors down for Argentine imports.

    There’s tactful good relations, and then there’s “sempai notice me”. Although, the Cosplay Crusader may well be familiar with that trope.



  • I do like that there’s a reasonably comprehensive website with docs covering a lot of common pain points, which is more manageable than fighting with searching through a galaxy of wikis of varying degrees of currentness and relevance.

    Reminds me of the celebrated docs of BSD systems.

    There’s also a case that going a bit away from “easy Windows replacement” is useful because even trivial users need to get some bearings shifted to avoid floundering when they reach something not-quite-Windowsesque. (I. e. dealing with updates and software distribution is an important lesson that isn’t obvious if they hide everything in an ersatz App Store)

    Of course, my first proper Linux setup was Slackware with a 2.0.30 kernel. I wanted the Unix-like Experience.