368
you are viewing a single comment's thread
view the rest of the comments
[-] muntedcrocodile@lemm.ee 23 points 5 months ago

When i first got here we hadn't even hit 1% yet. Open source scares Microsoft because if they fuck up they are done but we have a million distributions with a million different mutations its perfect evolution we cannot get worse only better.

[-] RecluseRamble@lemmy.dbzer0.com 11 points 5 months ago* (last edited 5 months ago)

Oh, it can get worse. If Windows market share should really plummet, it won't be replaced by a heterogenous distro utopia but some company like Canonical or Red Hat or a new one will get their distribution to fill the gap. And call me a cynic but I doubt this will be immune to enshittification.

But even that scenario is better than what we have with Microsoft and Apple. The FOSS world would still benefit like it does from the Steam Deck developments.

[-] barsquid@lemmy.world 1 points 5 months ago

We are already (mostly all of us) stuck with one company's systemd. We're already on some portion of what you're describing. As long as we use FOSS I think somebody will be able to fork any software that starts turning to shit with ads, LLM everywhere, spying on your activity, etc.

[-] PlasticExistence@lemmy.world 0 points 5 months ago

Well, no offense intended, but that is cynical. The only way for enshittification to hit Linux would be if only one group controlled it. When IBM/Red Hat discontinued CentOS, the community immediately moved to fill the gap with AlmaLinux and Rocky Linux.

That said, yes, things can always get worse. I don't think Linux is immune to having problems, but not on the scale of what's happening with Windows with their Copilot garbage.

[-] rodneylives@lemmy.world 0 points 5 months ago

My response to that is Flatpak. 16MB of software requiring 700MB to download and consuming 2.8GB of disk space. Linux absolutely can be bad, due to cultural issues.

(My example software above is Handbrake. I'm sure someone's going to "well actually" me about this, and I don't even care. I don't see how it can be justified, and I'm kind of curious to see if someone can do it.)

[-] kewjo@lemmy.world 1 points 5 months ago

it's great for applications that are notorious for requiring specific versions of libraries and can cause dependency hell. moves unnecessary system dependencies into a sandbox. for me this means i don't have to enable multilib to install Steam and pull in 32 bit libraries on my root.

while it does take a lot of disc space it doesn't duplicate dependencies in most cases. i would say you receive some good benefits at the cost of a bit more disc space, such as increased security, easy installs, explicit app permissions. it's great for when you have to install a proprietary tool in that you gain control of what it's allowed to access.

[-] rodneylives@lemmy.world 0 points 5 months ago

But it appears like we're in a situation where it's not used for specific situations, but for lots of different things. Just a few Flatpak programs starts to chew through a significant amount of disk space, and some programs are only being distributed as Flatpaks.

[-] kewjo@lemmy.world 1 points 5 months ago

flatpak distribution is generally done by the developer as a common packaging method. if a distribution wants a native install it's up to package maintainers of the distribution to support the application. although the package maintainers have to make sure they're packaging the right versions of dependencies which becomes a problem known as dependency hell.

in your example of handbrake it's true the main application is pretty small but that's because it relies on libraries and is a wrapper for ffmpeg. even if you install through a package manager you still need to compare the total size of dependencies.

the disc space usage becomes a problem due to installing libraries both natively and in sandbox. however if you keep a relatively small system install and install applications through flatpak the disc usage will be pretty negligible. if disc space is really a concern then using something like btrfs with compression+dedup would probably solve most problems.

[-] rodneylives@lemmy.world 1 points 5 months ago

It just seems like it's a lot of papering over a fairly substantial problem. While the example I gave was Handbrake, which does seem like it should be a unique example, every other piece of software that I check Flatpak versions of also had ludicrously wasteful storage issues.

I'm aware of dependency hell, but it seems to me that most software doesn't have that as a problem, not if the libraries are sensibly maintained? After all, the fact that upgrading a library can improve all the software that uses it seems like it's usually a positive thing. And the ballooning storage requirements of Flatpak make it a tool that should be used occasionally, rather as a primary way to release software. Using a filesystem that can detect duplicates would help, but itself also seems like a special-case kind of solution, and not a great solution to turn to just to avoid what seems to me to be a significant issue.

[-] haui_lemmy@lemmy.giftedmc.com 3 points 5 months ago

Thats a very cool perspective. I hadnt considered this. Everyone seems to be hating on linux‘s fracturization but it does remind me of evolution now that you mention it.

[-] ricdeh@lemmy.world -5 points 5 months ago

Principally correct, but please note the difference between "open-source software" (OSS) and "free and open-source software" (FOSS). They are two related, but different philosophies, and principally, GNU/Linux belongs to the latter rather than to the former.

[-] Klear@sh.itjust.works 12 points 5 months ago

If FOSS ever fails, it's going to be because of ridiculously stupid pedantry like this.

[-] MonkeMischief@lemmy.today 6 points 5 months ago

"I'd just like to interject for a moment..."

[-] muntedcrocodile@lemm.ee 1 points 5 months ago

Well the principle i was talking about requires free forking which would make it foss.

this post was submitted on 24 May 2024
368 points (98.2% liked)

linuxmemes

21281 readers
20 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 members of the community for any reason.
  • 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.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 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. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS