this post was submitted on 31 Jan 2026
1107 points (97.5% liked)

linuxmemes

29896 readers
1275 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
  • Don't come looking for advice, this is not the right community.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
  • 5. ๐Ÿ‡ฌ๐Ÿ‡ง Language/ัะทั‹ะบ/Sprache
  • This is primarily an English-speaking community. ๐Ÿ‡ฌ๐Ÿ‡ง๐Ÿ‡ฆ๐Ÿ‡บ๐Ÿ‡บ๐Ÿ‡ธ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
  • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
  • ย 

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
     

    ๐Ÿชฟ

    you are viewing a single comment's thread
    view the rest of the comments
    [โ€“] TheGingerNut@lemmy.blahaj.zone 11 points 1 week ago (29 children)

    The core principal of GNU from which every other principal is derived is "I shouldn't need an ancient unmaintained printer driver that only works on windows 95 to use my god damned printer. I should have the source code so I can adapt it to work with my smart toaster"

    If an app is open source then I've almost never encountered a situation where I can't build a working version. Its happened to me once that I remember. A synthesia clone called linthesia. Would not compile for love nor money and the provided binary was built for ubuntu 12 or something.

    Linux was probably ready for the 64-bit appocalypse even before Apple for this exact reason. Anything open source will just run, on anything, because some hobbiest has wanted to use it on their favourite platform at some point. And if not, you'd be surprised how not hard it is to checkout the sourcecode from github and make your own port. Difficult, but far from impossible.

    Steam games do not distribute source code, which means they break, and when they break the community can't fix them. They can't statically link glibc because that would put them in violation of the GPL (as far as I'm aware anyway). They are fundamentally second class citizens on linux because they refuse to embrace its culture. FOSS apps basically never die while there's someone to maintain them.

    Its like when American companies come to Europe and realise the workers have rights and then get a reputation as scuzzballs for trying to rules lawyer those rights.

    [โ€“] LodeMike@lemmy.today 1 points 1 week ago* (last edited 1 week ago) (12 children)

    Okay so bundle glibc. As far as I know link systemcalls are set up to look in the working directory first

    Why would statically compiling it violate the GPL?

    [โ€“] qqq@lemmy.world 2 points 1 week ago (4 children)

    It wouldn't; glibc is LGPL not GPL. The person you're replying to was mistaken.

    [โ€“] TheGingerNut@lemmy.blahaj.zone 1 points 1 week ago (1 children)

    You know what, that explains how they can exist on linux at all. Because from what I understand, if glibc was GPL and not LGPL, closed source software would basically be impossible to run on the platform. Whichโ€ฆ maybe isn't the best outcome when you think about it. As much as I hate the Zoom VDI bridge, I don't want "using windows" to be the alternative.

    and yeah, from the source you provided, I can see why they don't statically link. "If you dynamically link against an LGPLed library already present on the user's computer, you need not convey the library's source". So basically if they bundle glibc then they need to provide the glibc source to users on request but if they just distribute a binary linked against the system one then that's their obligations met.

    Welcome to "complying with the LGPL for the terminally lazy", I'll be your host "Every early linux port of a steam game!"

    [โ€“] qqq@lemmy.world 1 points 1 week ago

    My understanding of the linking rules for the GPL is that they're pretty much always broken and I'm not even sure if they're believed to be enforceable? I'm far out of my element there. I personally use MPLv2 when I want my project to be "use as you please and, if you change this code, please give your contributions back to the main project"

    load more comments (2 replies)
    load more comments (9 replies)
    load more comments (25 replies)