Elektrine lite

← Feed

@istewart@awful.systems

2026-11-18 14:47 UTC

The second post in the thread is a great distillation and thesis statement: hachyderm.io/@dalias/117635183290482925 That is to say, the majority of the harm from proprietary software is not that it being non-free keeps folks who want to use and understand it from doing so, but that it’s systems of opaque rules people are forced to interact with in ways where not understanding those rules puts them at a disadvantage. Making it so a few specialists can understand the rules (by having the source) only helps minimally. I was thinking about this last night. From an end-user perspective, for example, subsystem-specific text configuration files in a top-level /etc directory and dotfiles in the user home directory are less opaque than the Windows Registry. But they are still non-obvious, non-standardized, something you have to spend time wrapping your head around that doesn’t necessarily offer skill transfer to anything else. The movement, such as it is, stood on pride that we had achieved a freely-available replica of something that was expensive, resource-heavy proprietary software in the 1980s, and never moved on from that. Backslid, even. What are we doing here?

Replies (1)

  • I think a lot of the difference is in how the windows registry hides the opacity somewhere that most users will never actually look for it. Like, for a non-technical user it had may as well not exist, while for that same user a Linux system had may as well have a great big door labeled /etc/ with a “do not enter” sign in great big letters. Except then you want the system to do something different and now you need to enter it and pray that your guide to the arcane secrets is right and won’t just break something somewhere else.

    Open ##5558839