this post was submitted on 25 Nov 2024
156 points (75.8% liked)

Linuxsucks

372 readers
37 users here now

For knowledge and awareness about what using Linux is really like and pointing at its cultish toxic community. We also cover FOSS /FLOSS failures, and issues with GPL since it relates to Linux. Moderation is heavy handed to appeal to our target users.

Rules:

  1. FOSS (especially GPL) advocates and Linux (specifically GNU/Linux) evangelists aren't welcome (GNU Hurd will count as Linux). -We ask that you block us and we will perma-ban for violations of this rule.
  2. Try to stay on topic (that is LINUXSUCKS!). No bashing other OSs or each other. We aim for a cohesive non-toxic community with the interest of cautioning people / would be victims from Linux. At our discretion, we will remove what we consider pollution.
  3. Moderators run the sub, not the users. It's not democratic, and we don't care how you think it should be run. -Feel free to make and run your own community.
  4. "Not your Billboard" -Over-represented companies will have positive posts removed and appropriate bans may be issued. -Those companies included so far will be Valve/Steam/Proton, Google, and Brave (browser).

Linux/FOSS can damage hardware or firmware

Mixing Apps Bloats LiGNUx

Linux running servers isn't a brag

Is Linux Running Games Near Windows Performance Impressive?

Wasted Ram on Different Toolkits and Distro-Agnostic Packages in Linux

Critical ISS Systems do NOT run Linux

Abandoned Software is Dangerous (and common on Linux)

FOSS Devs Quit and Sellout on Unappreciative Userbase

Firmware Flashing is Riskier on Linux

Linux Community Toxicity Ties Directly into Inferiority Complex Psychology

The Positives of Telemetry

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] auzy@lemmy.world 0 points 2 years ago (2 children)

Not really.

There is a good reason Windows does it.

To guarantee the running state of the system, and to ensure everything runs using the components and versions they were designed to use

[–] JoYo@lemmy.ml 1 points 2 years ago (1 children)

I can easily install multiple versions of coreutils and glibc without issue.

[–] auzy@lemmy.world 3 points 2 years ago* (last edited 2 years ago)

Cool. You do that

Are you going to install multiple versions of every library?

What if it's a security fix and it's in issue in your desktop environment, etc

Coreutils and glibc aren't the only libraries on your system

Some apps might use static linking too so might need to be restarted. Other libraries might be loaded long after the app is started. If you swap libraries half way, it's not great too

What if you're copying large files half way and run out of space. That nuked my Linux mint install

Linux distros don't just copy Windows. They wouldn't put in the extra effort unless they have to.

Do you think a bunch of developers sit around and don't evaluate why they're doing things? And instead just copy from Windows? Nah mate. They do it for a reason

The cool thing about doing it this way is if boot fails, you can rollback easily too. If you're installing core components randomly, your system might only fall to boot a week later

[–] corsicanguppy@lemmy.ca 0 points 2 years ago (1 children)

No. Its because windows read-locks everything.

In Linux we have post-install scripts to ensure relevant stuff gets restarted as long as it was installed properly. (The improperly installed shit can go fuck itself)

The only time you need to reboot is when you've upgraded your kernel without kstuff/ksplice or you've glanced at dbus a little sideways.

[–] auzy@lemmy.world 4 points 2 years ago

sigh

Post-Install scripts don't fix 100% of the issue and dynamic lazy linking is a real thing.

The read-only thing really isn't the main issue here, and everyone including windows has a way to do post installation stuff, and has a service manager

As an example, a few years ago my system kept erroring due to a gstreamer update. Reboot fixed it (I only remember it because the bug reports were only recently closed).

Probably because apps had half loaded old versions, and were lazy linking new versions.

Furthermore, without doing this, self-recovery is difficult. Because if you update something today, and reboot a week later and your system doesn't boot, you have no idea what caused it. You'd have to keep rolling back. If you do it on reboot, you can snapshot, update, and if system fails, then rollback automatically after losing nothing.

There's lots of good reasons