New users are expected to keep copying and pasting commands from their browsers to their terminal which compromises some Linux security defenses.

To me, this is the worst issue here.

Even large Projects suggest things that are basically curl | sh – without even mentioning anything about how this could be problematic.

New user are “trained” doing this.

Every project suggesting it should be not only opposed but actively fought against until they change this bullshit.

Yea this is a very unpopular opinion.

Not all distros ship SELinux and the ones that do, don’t actually configure it securely.

Convenience issues.

New users are expected to keep copying and pasting commands from their browsers to their terminal which compromises some Linux security defenses.

Everyone literally says not to do that, including popular content creators.

KDE, GNOME and Sway are the only functional Desktop Environments/Window Managers that support Wayland all, while the Other DEs are not even close to shipping with Wayland.

Wayland is massive and probably will never actually be finished. Also implementing it basically means rewriting the whole DE (not really but it’s a ton of work).

Most if not all of the Linux Distros in 2025 ship with Grub bootloader, which suffers from a lot of problems, instead of using the bootloaders that does not support BIOS and will improve the reliability of booting and provide a more stable experience.

That’s called “planned obsolescence”.

• Redundant (it’s not the only security mechanism)
• False / misleading / not-a-Linux issue (more of an internet culture issue).
• FUD. Wayland is not the only way to go; X11 is pretty mature.
• FUD with intent to sell Microsoft’s “Secure Boot”.

Nice try but doesn’t deserve wasting more time on. -4.4/10.

Is SELinux really that important for the average desktop user? I mean we have a lot of concepts like different system user accounts which run services, namespaces…

And I feel we’d need more sandboxing and a permission system for desktop apps so they have to ask before reading your Documents directory and access the webcam. That’d do way more than SELinux as is… And we kind of have none of that to begin with. (…except software installed as Flatpaks, to some degree.)

Okay, I call bs on the Wayland part

When was the last time you suffered from a exploit on X11? Most distros even setup X11 to be localhost only

X11 has a lot of problems, but claiming it is insecure by default is kinda bs

Changing from UDP to TCP when you aren’t using TLS at all doesn’t solve the issue

Not all distros ship SELinux and the ones that do, don’t actually configure it securely.

You’re welcome to work with distro maintainers to fix this instead of just complaining about it.

New users are expected to keep copying and pasting commands from their browsers to their terminal which compromises some Linux security defenses.

This is a big problem

Most if not all of the Linux Distros in 2025 ship with Grub bootloader, which suffers from a lot of problems, instead of using the bootloaders that does not support BIOS and will improve the reliability of booting and provide a more stable experience.

You’re welcome to work with distro maintainers to fix this instead of just complaining about it.

1. I agree mostly yeah it should be by default(but also depends from usecase too if we installing distro as many people doing on old hardware it would even more slow PC)

2. Copy pasting would damage mac os, windows including too so it’s just human factor

3. Wayland is protocol not server and to implement full stack u need a lot resources and not small team meanwhile x11 it’s ready to go graphical server universal one

4. About this some distros installing systemd-boot if installer detecting efi variables if legacy system it installing grub.

All depends from threat surface attack and what we are trying to defend.