I write English / Escribo en Español.

Vidya / videojuegos. Internet. Cats / Gatos. Pizza. Nap / Siesta.

This user’s posts under CC-BY-NC-SA license. Ask me if you need a different permission.

  • 2 Posts
  • 156 Comments
Joined 2 years ago
cake
Cake day: July 26th, 2023

help-circle

  • I think you didn’t get my point. I meant in Windows I have to fight to install the printer, but in Linux I can’t even do that because Linux is too good and handles the printing perfectly for me.

    That said if what you are suggesting is we could create issues in relevant repos to make the hardware install process in Linux more… interactive like it is in Windows, with an assistant that tries in vain to download drivers from the internet, a “shield” that asks you to load the drivers from a floppy disk A:\ and that needs a hardware reboot every time you plug in a new USB mouse… hmmm… maybe you are on to something.




  • if you have to list more than one thing per thing the landscape may not be there for a full replacement

    And it would be even less if there had to be only one thing per thing.

    One of the strengths of the FOSS metacommunity is the variety in designs and results. Big Corpo abuses economies of scale and locks you in with a “one shoe fits all solution” because they under the table also chisel and file your feet; FOSS has (largely) no such restrictions so they can afford to try things and see what results and, more importantly, what evolves. Not everything has to be a copy of corporate, and we shouldn’t act as if it had to be.




  • For me it’d be two aspects:

    1. lack of knowledge and clarity whether my use case is affected and to what degree.
    2. worry over the extra operational overhead.

    For (1), it’s not necessarily about the explicit workflow, like the GUI apps and stuff; but also the implicit workflow as well: the stuff going on with the machine because you are not touching it (even if it is because you’ve touched it before).

    Some examples. I need to forbid PA and have either ALSA or Pipewire (or both) with alsa-ucf disabled because of a hardware bug in my machine’s audio chipset. I can one-time accommodate the required kernel boot time options and ALSA configs without issue on Debian, can I do that on an immutable? Am I forced to the barely-progressing-past-failure that is wayland, or can I use the Xorg setup that has for decades proven to me to work? Do I get to escape the enforced GTK compose key mapping on my own, or do I need to break immutableness to fix it? Can the programs that I launch through wine on the user account I set up for work, interact with the apps I have on my normal user’s desktop (incl. copy-paste, desktop screenshots, sending global key events for stuff like Teamviewer, Supremo, Anydesk), or do I need to fall back to a Virtualbox VM?

    And for (2), it’s quite simple. I have a 8 GB RAM machine. I’m barely managing to survive this world of nu-web development where hello world apps download 150 MB of a typokit SDK from Cloudflare or something. If an immutable environment means that everything even the Linux equivalent of W95’s notepad.exe is now containerized, that’s an extra memory and resource overhead that my system likely can not serve and that I don’t really have an use for anyway (why would I want a text editor to not load up a text file I told it to load???).



  • Hopefully no one is asking developers to be virtuous (even tho, to be fair, if we are going to be asking that we should also expect the code to be wholly bugs-free!), but how many times they actually “keep their beliefs to themselves and focus on technical issues in the project”? On whichever side. It’s just not a thing that can reasonably be avoided all the time between humans.

    But the reality of these times is that behaviour outside the field of programming is representative and/or predictive of behaviour in the field of programming, when it comes to literally working with other people. And this is not only about the act of commiting changes or filing PRs, it’s about the why of programming and the ways of delivery as well. Someone who strongly associates with barbaric beliefs is less likely to want to spend their spare time working in peace for all, and more likely to be wanting to work on software that at least in some way carries or represents those beliefs, for example in capturing and using user data, or in aiding systems used by the military to kill children of “non-citizens”. So being “absolutely” uncaring does not really make sense.




  • What does “empathy in communication” have to do with a software project?

    Not having read Stein’s work, I can only mostly guess it’s related to the emphasis on the “communication” part as it applis to effective communication of duties, milestones, failure modes and reactions in a project. Torvalds’s tirades for example were awesome and most of the time well-deserved for the idiot trying to accidentally the kernel, but are quite more of a bummer and a momentum-killer when looked at at a project-wide scope.

    I’m all for empathy, don’t get me wrong, but ideally software projects are more focused on technical correctness than feels

    (Not) sorry to say, that age has long sailed. Remote teambuilding, capitalism and AI have made it that we now need to actually care and be watchful why or how something is being made to work, on the technical sense. Just look at the situation with Mozilla or Signal (offering systems that can be described as free, but are being offered so in a rather adversarial manner).