Attempting solidarity pragmatically.

Also @cakeistheanswer@lemmy.world @cakeisthenanswer@lemmy.fmhy.ml

  • 0 Posts
  • 16 Comments
Joined 1 year ago
cake
Cake day: July 23rd, 2023

help-circle
  • Its the same problem as standardized Unix systems in the 90s. There’s more ideas on how to implement hardware than there are hands to integrate driver software.

    When it comes together it’ll be because we either make the manufacturers warp around something like POSIX, or provide a common target on phones like the steam deck.

    Otherwise every hardware generation will get the undescribable misery of supporting the last one, from the one they’re on, while writing the next one. The problem tends to compound.


  • This is always a spectrum from how long it was since the last Debian stable release. So about 2 years max.

    Modern release cadences make it crazy anywhere but Debian, but security patches are very timely. If you’re dealing with newer features, driver support or java/npm packages you’re probably also outside the typical defaults, but there’s generally some people working to keep the common ones up to date.

    Still not my preferred way to handle updates and in some cases… kind of abusive to the maintainers who constantly haVE to deal with bug reports from “out of date” Debian users. The xscreensaver maintainer has some choice words. But it works, has for years with no sign of slowing.


  • K, teachable moment maybe.

    How complicated do you think a web browser is? Out of the box there is support for 30 years of web and file systems, support for socket types that will never be commissioned again and a pipeline to every native media format.

    It’s complicated, it’s essentially an OS. with perfect backward compatability. (Mostly)

    I have an increasing amount of bile for the Mozilla Corp, but if you’re on Lemmy you probably noticed corporations don’t make the best decisions for you… My question is how many of the options do you see in about:config do you think chrome and safari don’t show you?

    Mostly to their benefit I’d add, except if they set them maliciously you’ll never know.



  • Gentoo is an open book test on compile flags at all times.

    All you have to know is all your system variables, compiler flags that exactly two distros use, init, daemons and hardware and it’s great!

    On some level I admire the people who know that stuff, but I’ve had my OS compiled for me for a long time. I loved portage once I figured out how to use it though.

    I might add some version of Suse (open or enterprise) to that list though. Last I checked there were a bunch of shops kicking the tires as cent os shut off. Didn’t keep up on how that turned out.


  • I like fuzzel, had a few issues with dpi scaling on wofi out of the box.

    Easy to integrate clipboard/window select/dmenu binds and a way to distinguish indexed entries from straight text was a plus.

    Honestly unless you’re going out of the box to something new (Walker and anyrun caught my eye) dmenu has had everything I needed for years… But I don’t want to set it up again. Not again.


  • It gets better!

    I took a deep dive on fonts my first week(they were fuzzy). I now know a lot about things I almost never use or set, but every win will give you a piece of the whole thing.

    Eventually you figure out the “core” (that stays the same everywhere and you don’t have to do near as much work to tack on the extras.

    It’s big and complicated because you’re replacing windows with the hundred individual things windows does, each were made by someone else, in some cases decades apart.

    Somehow it all works pretty well, but we stand on the shoulders of some giants.

    Edit: I also don’t like manjaro, but someone here has covered why better than I would have. I run endeavouros and would recommend if you want arch with less config, but it is arch. Mint is where I have been pointing people to start recently.



  • I use the Debian social contract as an example of the an unmitigated good in open source.

    That doesn’t mean the org always live up to it, but that’s partially why there are battles for things like representation inside. I wouldn’t extend the benefit of the doubt to canonical, and I prefer rolling as opposed to security ported updates on my own hardware, but they made what you see possible on the internet in large part because people came together to make a free platform.

    The orgs dogmas look like product of a bygone age to be, and changes to environment in software is probably as hostile to their approach as ever. I’m amazed they’re not more dysfunctional just from the outside looking, it’s a rock solid implementation.




  • Definitely worth running through vim tutor at least once.

    It’s beyond typing speed, things like piping out strings to utilities is using one program to write another, you aren’t just getting faster because of access, it’s a paradigm shift.

    Edit just for fun: im a non Dev dummy who happened to grow up in a Unix household. Even having dropped vim for helix and bounced around the MS admin/Apple IT space for 30+ years. When I switched to Linux I could still remember binds I’d set up and last used at 9.

    Kinda like riding a bike.



  • This is incredibly true. The hardware manufacture process is a slow turning and cost centric wheel, but it’s always forward looking. If it doesn’t exist today you are building around compromises made outside the scope of your concerns.

    Anyone whose had to work on DEC or Sun hardware can describe in excruciating detail about how minor implementation differences in hardware cascade down the chain. (Missing) Rubber washers determined a SAN max writes once, lest the platters vibrating cause the chassis to walk across the floor.

    ‘Universal’ support is always a myth, and carving up what segment to target is shooting one moving target while standing on another one unless you have exclusive control of implementation of the whole chain (apple).