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

help-circle

  • The Apple II’s big selling point, compared to the other two big brands introduced in 1977 (the Radio Shack TRS-80 and Commodore PET) was colour.

    But it was a weird and colour scheme that took advantage of clever Wozniak hacks to make it viable on a cheap machine. Good video hardware, and enough memory for the colour display, were spendy. That’s why even into the 1980s you’d have machines like the ZX Spectrum with limitations like “every 8x8 block can only have 2 colours” which used less memory, and 40-column screens that were readable on TVs instead of dedicated high-res monitors…




  • 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 never realized the tattoos were photoshopped.

    I assumed they used a random stock photo that had a convenient pose to add the shirt onto, that happened to have a tattoo.

    Of course, I also figured using a photo with too much ink would 1) distract from the merchandise and 2) make the stock photo model too recognizable. (Oh, they clearly used Getty #8675309, “Fat White Guy With Mediocre Barbed Wire Tattoo”), but plenty of the pics are identifiable enough to use for a police report.



  • Also on modern firebreathers.

    I like runit better than systemd, the packages are current, and it has most of what I want in the main repos.

    I also found the documentation excellent in thst it’s a cohesive list of real-world topics rather than a 500-km-deep wiki or forum archive.

    I should try a modern Slackware one day. I loved it back before I had broadband and just ordered a burned CD for each new release, but I should try following -current and the Slackbuilds stuff.


  • 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.


  • We get, for some reason, a huge number of window replacement contractors coming door-to-door. Because I really want to be high-pressure sold $10k worth of low quality glass from the people who are running big enough marhins to put a full page colour ad in the local newspaper every day to go with their 6 hours a day of local TV spots.

    I actually said to one “We’re a Linux household. Not interested in Windows” and slammed the door on them.

    I now realize cocking a rifle would have made the effect even better.



  • No, this is a general practice-- I see it a lot with third-party vendors who want you to integrate with their services. They’ll expire the documentation portal password after 90 days, but the actual user facing service still accepts the same “password123” that’s been set since 2004.

    I suspect the pattern is to protect the vendors from developer scrutiny: by the time you’ve jumped through enough hoops to read the docs and realize it’s trash, the execs have signed the contracts and the sunk costs are too high to bail out.

    Also add another 6 months to actually get the credentials for the test environment.





  • With American comics, it’s not even the shattered continuity, it’s that availability is a mess because some of the franchises are so ancient and collectible.

    If I want to read through One Piece from the 1997 start, my library probably has/can inter-library loan all 105 volumes, or I can go to mainstream retailers and get any I’m missing without a huge fracas.

    If I want to read Batman from the 1940 start, I’d better hope some of the rarer issues come up at auction in the near future AND that I can mortgage my house to afford them.

    I’m amazed they never put out a DVD-ROM collection that’s “Everything Marvel/DC did prior to, say, 1990, as PDF scans” just so mere mortals have a chance to enjoy the experience of completionism.




  • 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.