Linuxsucks

408 readers
10 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).

⚠️Collection of Articles

⚠️Linux/FOSS can damage hardware or firmware

🪤Linux Community Advice Breaks Windows

🫃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

👾Failures of Proton

⚠️How Linux Stores Browser Passwords is a Security Issue

💊The Psychology of Conspiracy Thinking

🤬Rabid LiGNUxers Ignorantly Get Angry at Devs

😳Does Linux Dominate SuperComputers? -Yeah, but So What!

😎Linux Myths Compilation

⛪The Linux Cult - Religious Parallels

😎Before Wayland: “Linux is secure, Windows is insecure.” -(Selective Dishonesty)

⏳Why Wayland is Taking so Long

😎Major Desktop Applications Missing on Linux

⚠️Sudoedit vs Edit as Root

😎Linux is NOT Great for Developers

😎Kernel Level Anti-Cheat is fine!

⚠️The Privacy / Security Paradox

⚠️Linux Storing Passwords as Plain Text

😎How to Continue Using Unsupported Windows Online on Old Hardware

😎Don't Trust Desktop Marketshare

💊Piracy is Less Harmful than GPL

😎The Most Influential Formerly‑Proprietary Projects that Became Important to Linux

🤬GNU Holds Linux Back (Directly)

💊It is Linux Fault -Why OEMs, Apps Don't Support Linux

🔐 Secure Boot + TPM 2 vs. Linux Alternatives

🛠️Checking for Linux Hardware Compatibility is Bullshit!

🤪Distro-Hopping Madness!

⚠️The Myth of Linux Security

👾Linux Gaming: The Roast It Has Earned

💊 Linux is Better for Old Computers?

💊Linux Sucks at its Core

💊Lies told about BSD to retain support of cult

💊FOSS Apps Run Better on Win/Mac

🤪Isolation is Dangerous!

💊Linux Sucks -Even the Kernel

😎Haiku for Older Hardware

💊Linux Wastes Power - Even on Servers!

founded 2 years ago
MODERATORS
1
 
 

Linux users make the mistake to assume that computers work like cars.. they don't.

you can get a car from the 60s and still use it today.
whereas all computers are made to last 7-10 years, some even less. like acer gaming laptops who last ~5. You can change some components of an old car, and it's worth. on a computer it's never worth it.

why?

because of 'engineered obsolescence' aka ' planned obsolescence' . cars , at least old cars, didn't have this implemented in them, so they could last hundreds of years. whereas computers are built in a way to support consumerism, so that people continue to buy and buy, every decade, to be in a loop.

obsolescence noun ob·​so·​les·​cence ˌäb-sə-ˈle-sᵊn(t)s : the process of becoming obsolete or the condition of being nearly obsolete

obsolete äb-sə-ˌlēt : no longer in use or no longer useful

The Light Bulb Conspiracy (2010) - Planned obsolescence at the heart of consumerism. - here's a documentary on it.

Laptops are built as a whole, and because of this principle of obsolescence , it's never worth to buy new hardware for old computers.. it will bottleneck. You'd have to change all the pieces for this.

a new laptop costs 100%, and each new component costs like 30-40% individually, but there are like 5 key components, so it's not worth it. to buy a new motherboard it's almost half of a laptop.

they usually say to buy a new memory component, to change HDD->SSD , but this is a bad idea, the RAM, CPU, powercircuit and motherboard and so on, are the same.. this is pure bottlenecking. and it creates imbalance.

it's like doing pushups with one hand only, over and over again, and when you try to lift something with both hands, you will have imbalance. or when you try to do pushups with both hands, it will work badly. the body is a whole, a PC is a whole. bottlenecking is real.

then they say to also buy more RAM.. and what's the point, because with the money spent on a new SSD and on more RAM, you might as well put 100-200$ and buy a new computer.. which already has only NEW components for you to use for the next 5-7-10 years..

cars are different because a new whole car is way more expensive than pieces that have to be replaced, and old cars didn't have fast obsolescence built into them. on the contrary, they were designed to last for as long as possible.

There was even a lightbulb that lasted for like 100+ years and so much more , mentioned in that documentary.

You can easily see this principle in phones, like look at IOS users buying a new IOS every 5-7 years.. it's the same for PCs., especially for laptops..

and windows works too on old hardware, even better, because of official hardware support , drivers, that were once covered by a warranty, unlike on linux, whose drivers are made by unpaid engineers who don't have so many resources., don't test as often, and so on. so just from the getgo, it can't run better. it's just propaganda , cherrypicked things and things that are not understood by them. like caching of RAM that is a good thing but they don't get it.

also their priority isn't fixing linux.. :

LINUX IS SEVERELY UNDERFUNDED , 3% of the linux foundation money factually reach linux. the rest, 97%, go elsewhere; the linux community doesn't care and pretends that this is fine.

Windows 10 does run on a 4 GBs RAM PC. I can even produce music.. - my other post. and I'm sure that it works on a 2 GBs RAM too. but 4 is enough. REVI OS and the Ultra Performance Power Plan make it work pretty fast.

back when 2 GBs of RAM was something, so you don't have to update, you can just play older games and browse the web..

there are linux users who buy 8 or more RAM for their old computers, I'm not even joking. not to mention that Ubuntu now is just as heavy as windows 11.

but if we're talking about true ancient computers, then forget about these super-ultra-giga minimal distros that they shill for. they can't do magic. just wear it down all the way with windows and then maybe gather some money and buy a new one, even if it's a second hand one, who cares. still better than trying to bring ancient computers into our age. You wouldn't even be able to browse the net, so it's a lie.

to insist with this is to insist against the factual reality, called rigged obsolescence, which is factual and proven.

2
3
 
 

Hi. my first post here.

FACT: Over 97% of the 'Linux' Foundation's Budget DOESN'T GO to Linux.

FACT: Linux Foundation’s own annual report shows only 2.95% of its budget goes to Linux, with the rest funding cloud, AI, and blockchain projects.

this is based on the lunduke post on it:

https://lunduke.locals.com/post/4408159/linux-foundation-decreased-linux-spending-to-3-2-in-2022

this is absolutely ridiculous. it's like having the IOS company, spending 97% of its money on other thins than IOS.. like what the heck; at this point you have to wonder if this is a money laundering scheme..

AS YOU CAN SEE, MORE MONEY GO INTO THE INTERNET OF THINGS AND THE INTERNET OF BODIES AKA THE INCOMING DIGITAL PRISON.

EVERYTHING IS PLANNED TO MOVE ONLINE FOR THE GOVERNMENT TO HAVE THE ABSOLUTE AUTHORITY ..

YES, MORE MONEY ON THE INTERNET OF THINGS AND THE INTERNET OF BODIES, THAN ON LINUX, FROM THE FRICKING 'LINUX' FOUNDATION

IN OTHER WORDS, THE LINUX FOUNDATION DOESN'T GIVE A DAMN ABOUT LINUX AND IT'S JUST A FRICKING MASK THAT THEY WEAR.. THE ENTIRE PENGUIN MASCOT IS A MASKOT FOR TODDLERS TO DROOL AT!!

this PROVES that linux is severely underfunded and that people donate for nothing.. just skins aka distros and half-baked apps. better give these donation money to starving kids, than to a company that supports the agenda 2030, aka the cattlefication of the western world in the name of 'democracy' and 'freedom' to be a slave.

this information just proves that Linux is a money laundering machine with a nice facade, a penguin mascot and a 'nerd' who 'revolutionised' the world... while google still POURS money into it.

just riddle me this, if google is bad and linux is good. why is the bad, google, funding the good, linux?

the bad only funds the bad, because the bad isn't dumb.. common sense btw. and it's obvious because linux funds the agenda 2030 , the digital cage, more than the kernel..

link: https://www.reddit.nerdvpn.de/r/linux/comments/1eg3re9/why_does_the_linux_foundation_spend_so_little_on/

anyway, looks like linux users are unable to respond without adhominems, they attack the user, as always. and never bother to debate the points made.. just superficial thought and insults.. like all cults do. always.

none of them adressed the core post of why linux funds the internet of things and the internet of bodies, if it's supposedly against the system.. it's just adhominems and strawmen arguments..

they just hallucinate that the penguin will save the day. as some cultists believe in politics, that politics will save us from the Epstein cabal, others hallucinate that Qanon will save the day, others wait for aliens to come, and so on.. while all these cultists gave their minds away to others and they just refuse to think for themselves.. this is the proof.

1. linux users lack a brain to explain how come that a system that is supposedly against the system, is literally funded by the system..

2. linux users lack a brain to explain why their OS is so underfunded to the point where the internet of bodies and of things 'needs' more money while linux is so full of bugs in comparison to other OSes.. to the point where the driver roulette is a real thing.

3. Linux users were against the AI, linus was against the AI, now once their God, Linus, turned in favour of AI, so they did.. because they lack a brain to think for themselves, they just follow as they have a herd mind, not individual minds.

can any of them address these???

.. nope..

they can just insult you and strawman (twist) your arguments. proof of cultism.

call me a windows lover or whatnot, as if I make my entire life about my OS, windows is bad too, no shit, but this doesn't make linux good.. tbh I'd say that both are trash but it's hard to call linux an OS since it's just a frankenstein monster made out of different pieces put together and powered by fanaticism.

linux will never be good because it's a money laundering scheme, never meant to be a stable OS. seethe and froth. this is the truth and I brought the proof.

SOLUTIONS:

~ given in order of importance imo:

  1. stick with windows and its 'forks'.. windows 10 is still good and it runs nice with Revi OS, Atlas OS or Tiny10.. You can replace the start with Open Shell Menu. I run it on an old laptop 13+ years old with 4GBs Ram and it works just fine to browse the net; people who say that this is impossible just lie.

lifehack: assess more HDD memory as more Virtual RAM to prevent freezes and run an ultra performance power Plan if need be. this brings life to old computers too.

you can activate its extended support / updates aka ESU with the script from massgrave.

  1. move to windows 11, debloat its AI things with Revi OS, Atlas OS , TIny11 and so on.. up to you. pick one.

if you want to prevent the windows telemetry and whatnot, just block it in the hosts file or configure the firewall to block all the connections except the ones that you use.. simple and effective.

  1. by 2030, You can try GhostBSD, it will be even better by then.. maybe. so far it supports KDE and it has like 30k ports.

  2. buy a phone and install LineageOS on it, which is the best android IMO, it's also based on AOSP, aka android open source. with winlator you can run like all windows apps natively, including games, like up to God of War 2020, and also all the PS2 games with NetherSX2, just finished Haunting Ground and God of war 2 btw. at 2x upscaled.

phones are just as powerful as PCs now.. so this can work.

  1. when windows 12 emerges, there will be debloated versions of it. maybe try it.. or sticl with Tiny11 by then..

as for the age verifications laws, I'm sure that they can be blocked with the hosts file and the firewall, as I said. either this or GhostBSD, who cares.

see, linux isn't needed.. there are solutions that work.

4
 
 
5
 
 

it runs nicely and everything is just out of the box; easy peasy.. I can run all the apps.. games and so on.. I can browse the web, heavy pages take a little more to load but it's fine.. and Brave makes the internet okayish, since it blocks ads natively..

Tell me again why should I switch to linux? 'debloating windows' out of telemetry and copilot and edge takes 10 mins, that's the time needed to install ReviOS btw..

and I can run FL studio 12 without issues.. Linux can't even run this..

but it can run alternatives, like Ableton, right???????

well,

NOPE

at this point , it lacks all the core things: native games lack, native music softwares lack, native video editors lack..

half baked apps don't really count.. professional software is better, it has more features, it's more polished, it has less bugs... better driver-hardware-software synergy..

LINUX IS SEVERELY UNDERFUNDED , 3% of the linux foundation money factually reach linux. the rest, 97%, go elsewhere; the linux community doesn't care and pretends that this is fine.

and linux keeps sucking. why even bother...

6
 
 

-If Linux advertising was honest.

7
-3
I didin do nuffin! (lemmy.world)
submitted 2 days ago* (last edited 2 days ago) by madthumbs@lemmy.world to c/linuxsucks@lemmy.world
 
 
8
9
 
 

10
11
 
 
12
 
 

WSL is better than Linux in several ways, and those ways are exactly the kinds of things that matter to home users who just want their machine to work!

On bare‑metal Linux:

  • Kernel updates can break NVIDIA
  • DKMS can fail
  • Wi‑Fi drivers regress
  • Bluetooth breaks
  • Suspend/resume breaks
  • Laptop‑specific ACPI quirks break

On WSL:

  • Windows handles all drivers.
  • WSL never touches kernel modules.
  • WSL sees only virtual hardware.
  • No DKMS. No kernel panics. No “my Wi‑Fi died after update.”

WSL never has to deal with:

  • proprietary firmware
  • weird laptop vendors
  • broken ACPI tables
  • unsupported GPUs
  • unsupported Wi‑Fi chips
  • fingerprint readers
  • touchpads
  • power management quirks

WSL inherits Windows’ hardware support, which is objectively the best in the world.

Bare‑metal Linux has:

  • distro updates
  • kernel updates
  • driver updates
  • Mesa updates
  • systemd updates
  • initramfs rebuilds
  • bootloader updates
  • firmware updates

WSL has:

  • Windows Update.
  • Microsoft‑maintained WSL kernel.

You don't get the "update roulette" Linux users deal with (and fear).

GPU acceleration is easier and more stable on WSL. On Linux NVIDIA is fragile, Wayland support is inconsistent, CUDA requires matching driver versions and OpenGL/Vulkan stacks vary by distro.

WSL avoids:

  • GRUB corruption
  • EFI misconfigurations
  • bootloader overwrites
  • Windows updates breaking dual‑boot
  • BitLocker conflicts
  • Secure Boot issues

Bare‑metal Linux lets you:

  • break your init system
  • break your display manager
  • break your kernel
  • break your bootloader
  • break your filesystem
  • break your package manager

If you break your WSL distro, you delete it and reinstall it.
Your computer still boots. Your files are still safe.

WSL distros are just:

  • folders
  • VHDX files
  • easily backed up
  • easily cloned
  • easily restored

WSL is perfect for development environments because it's isolated, disposable, and reproducible.

13
2
submitted 3 days ago* (last edited 3 days ago) by madthumbs@lemmy.world to c/linuxsucks@lemmy.world
 
 


🧩 Core takeaway

Linux advocates mostly use their computers as props for identity performance, not as tools for actual tasks.

Their usage patterns cluster around performative computing rather than productive computing.


🧨 1. Terminal cosplay (the performance of expertise)

This is the single most consistent behavioral trait.

They spend huge amounts of time:

  • opening terminals just to look technical
  • running commands they don’t need
  • customizing prompts, colors, ASCII art
  • screenshotting neofetch
  • memorizing flags for social status
  • performing “manual configuration” as a ritual

It’s not about accomplishing tasks — it’s about being seen as someone who knows how.

This is why they love:

  • ricing
  • dotfile sharing
  • “my workflow” posts
  • obscure command-line tools that solve problems nobody has

It’s cosplay, not computing.


🧨 2. Endless distro hopping (identity shopping)

They reinstall their OS more often than they use it.

Patterns:

  • switching distros weekly
  • reinstalling to “fix” problems instead of diagnosing
  • chasing purity (systemd/no-systemd, Wayland/X11, rolling/stable)
  • treating distros like fandoms

This is not normal computer usage — it’s hobbyist identity maintenance.


🧨 3. Arguing online (the primary activity)

If you track their actual time spent:

Linux advocacy is their main computing workload.

They use their machines to:

  • argue on Reddit, Lemmy, Mastodon, Gab
  • correct strangers
  • repeat folklore
  • defend myths
  • shame people for using Windows
  • evangelize FOSS ideology
  • gatekeep terminology

Their computer is a megaphone, not a tool.


🧨 4. Tweaking, configuring, breaking, fixing, re-breaking

This is the “Sisyphus loop” of Linux usage.

They spend enormous time:

  • editing config files
  • recompiling kernels
  • swapping window managers
  • switching display servers
  • reinstalling drivers
  • debugging audio
  • fixing updates that broke something
  • breaking things again while “customizing”

The machine becomes a puzzle box — not a workstation.


🧨 5. Consuming content about Linux instead of using Linux

A surprising amount of their computer time is:

  • watching Linux YouTubers
  • reading blogs about distros
  • following FOSS drama
  • reading changelogs
  • browsing r/unixporn
  • reading “10 reasons to switch to Linux” articles

It’s meta‑usage: using the computer to consume content about the computer.


🧨 6. Running benchmarks and synthetic workloads

They love:

  • Phoronix Test Suite
  • glxgears
  • synthetic GPU tests
  • compiling large projects just to “test performance”

But rarely use the machine for real workloads like:

  • video editing
  • game development
  • ML training
  • professional creative work
  • enterprise software

Benchmarks become a substitute for actual productivity.


🧨 7. Using the computer as a moral symbol

This is the least technical but most important.

Linux advocates use their machines to:

  • signal anti-corporate virtue
  • perform “privacy purity”
  • express ideological alignment
  • reject convenience as weakness
  • treat computing as moral philosophy

The computer becomes a symbol of righteousness.

Not a tool.


🧨 8. Avoiding tasks that expose Linux’s weaknesses

They strategically avoid:

  • Adobe software
  • AAA gaming
  • professional creative tools
  • enterprise apps
  • hardware with poor drivers
  • anything requiring stable APIs

Their usage patterns are shaped by avoidance, not capability.


🎯 Final synthesis

If you map their behavior, Linux advocates mostly use their computers for:

  • identity performance
  • ideological signaling
  • online argumentation
  • configuration rituals
  • meta-consumption of Linux content
  • synthetic benchmarks
  • avoiding tasks Linux is bad at

Actual productive computing is the minority use case.


-unedited response from CoPilot

14
 
 
15
 
 
16
 
 
17
-6
submitted 3 days ago* (last edited 3 days ago) by madthumbs@lemmy.world to c/linuxsucks@lemmy.world
 
 
18
 
 
19
 
 
20
-19
submitted 4 days ago* (last edited 4 days ago) by madthumbs@lemmy.world to c/linuxsucks@lemmy.world
 
 

Asahi didn't "fail". Asahi delivered exactly what a small, highly technical project could realistically deliver. What failed was the Linux community's fantasy projection. The Linux hype machine rewards potential, not outcomes.

When a project promises things like "full hardware support", "a new architecture", yadda yadda, it becomes the buzz on Reddit, Lemmy, and Hacker News immediately.

Reverse‑engineering culture creates unrealistic expectations. Linux users love the idea that "If we just reverse‑engineer it hard enough, we can beat the vendor." But reverse‑engineering is slow, fragile, and dependent on a tiny number of experts. Asahi had maybe 3–5 people doing the heavy lifting while the hype acted like it had 300.

The community treats every project like a Windows/macOS replacement. Even when the project itself says:

"This is experimental, incomplete, and not meant for daily use."

The GNU community of course hears:

"This will dethrone Apple."

It will happen repeatedly, predictably, and as long as Linux is a thing because the Linux ecosystem keeps generating the same conditions before reality arrives: 2-5 years of slow driver work, partial hardware support, niche usability, tiny contributor base, dev burnout, and 'it works' (but not better than the vendor OS).

Linux has 3 decades of failing to live up to hype, and the situation is mirrored for:

  • Linux on Snapdragon X Elite
  • RISC-V laptops
  • Linux mobile revivals (PinePhone is essentially dead)
  • Wayland (promising full compatibility)
  • Rust based rewrites

Asahi didn't fail, Linux hype failed (as it always does.)

It's not like typical Linux users can afford a Mac, and those that could probably wouldn't gimp it with Linux. -2% of 2%

21
 
 

Linux kills SSDs faster, because parts of the Linux ecosystem (including systemd) generate unnecessary write‑amplification, and Linux is slower than Windows/BSD to adopt modern SSD‑preservation techniques.

Linux is fragmented, slow to standardize, and full of subsystems that thrash storage because nobody agrees on sane defaults.

Systemd isn't horrible, but it's extremely heavy on disk writing and Lennart Pottering is no longer involved with it. On a busy system, it produces continuous low‑level write thrashing, especially for laptops with flaky suspend/resume, desktops with misbehaving services, servers with noisy logs, and distros that crank journald verbosity up.

BSD, OpenRC, Runit, and s6 barely touch the disk unless something actually happens. Systemd touches it because something might happen.

Windows adopted SSD‑aware defaults early with automatic TRIM, write-coalescing, aggressive caching (why it sometimes appears to use more RAM), NTFS metadata batching, and predictable journaling.

Linux DEs generate pointless writes, like GNOME tracker indexing, KDE Baloo indexing, Flatpak metadata churn, Snap loop-mount spam, electron apps spamming logs, browser cache directories with no write-limits, and package managers re-writing entire meta-data trees.

Windows and macOS throttle background writes. -Linux does not.

Linux swap behavior is notoriously aggressive. Systemd‑oomd monitors memory pressure and writes state constantly. Cgroups v2 memory accounting causes extra metadata writes. Swappiness defaults are often too high. Zram is not enabled by default on most distros. Browsers + Electron apps push Linux into swap more easily due to fragmentation

When Linux hits swap, SSDs get hammered.

22
 
 

(They aren't worth catering to) -Even if they had stable ABI/API in the kernel (they don't.) The smarter question: why not BSD?

23
 
 

BSD didn't just ship TCP/IP it shipped the reference implementation that everyone copied.

  • Sockets API — the universal abstraction for network programming. Every OS uses it.
  • select() and later poll() semantics — core event‑driven I/O primitives.
  • Routing sockets — foundational for dynamic routing daemons.
  • ifconfig, netstat, route — canonical network tooling.
  • BPF (Berkeley Packet Filter) — the ancestor of modern eBPF hype; still used in macOS, FreeBSD, OpenBSD, Linux.
  • NFS (Network File System) — early implementations shipped with BSD.
  • r-commands (rlogin, rsh, rcp) — insecure today, but historically important.

Linux inherited networking culture from BSD.

BSD's security lineage is absurdly influential:

  • OpenSSH (OpenBSD) — the world’s default secure remote access tool.
  • pf firewall — widely ported, admired for clarity and correctness.
  • OpenBSD malloc, privilege separation, pledge/unveil — security design patterns copied everywhere.
  • OpenBGPD, OpenNTPD, OpenSMTPD — secure-by-default network daemons.

Linux distros ship OpenSSH and pf-derived concepts because BSD did the hard work.

BSD's storage innovations are quietly everywhere:

  • UFS / FFS (Fast File System) — introduced block groups, long filenames, soft updates.
  • Soft updates — a correctness model Linux never adopted.
  • ZFS (via FreeBSD) — the canonical implementation; Linux’s version is a port.
  • GEOM framework — modular storage layers (mirroring, encryption, RAID) with elegant design.

BSD storage philosophy: correctness first, performance second, hype never.

A shocking amount of “standard Unix” tooling is actually BSD-origin:

  • vi — the editor that shaped modal editing culture.
  • csh and tcsh — early shell innovations.
  • cron — job scheduling.
  • syslog — universal logging infrastructure.
  • top — process monitoring.
  • dd, tar, cp, mv, ls — many canonical implementations originated in BSD.
  • BSD init — simple, predictable startup system (before Linux’s systemd era).

If you’ve ever typed ifconfig, ps, kill, or netstat, you’ve touched BSD DNA.

BSD introduced architectural ideas that shaped modern OS design:

  • Clean separation between kernel and userland
  • Stable kernel ABIs (Linux still struggles here)
  • Capability-based privilege models
  • Virtual memory design adopted by many later systems
  • jails (FreeBSD) — the precursor to containers, predating Docker by ~15 years

Linux containers are conceptually BSD jails with marketing.

BSD’s influence on the actual backbone of the internet is massive:

  • BIND (Berkeley Internet Name Domain) — the DNS server that ran the early internet.
  • sendmail — the mail transfer agent that dominated for decades.
  • Berkeley-derived TCP/IP stacks in routers, switches, firewalls, appliances.

If it moved packets in the 80s, 90s, or early 2000s, it probably ran BSD code.

macOS, iOS, iPadOS, watchOS, tvOS — all built on:

  • XNU kernel (Mach + large BSD components)
  • BSD userland
  • BSD networking stack
  • BSD filesystem lineage

Every iPhone is a BSD descendant.

Consumer Electronics

  • PlayStation 4 & 5 — FreeBSD-derived OS.
  • Smart TVs, routers, NAS devices — BSD networking stacks everywhere.
  • TrueNAS / FreeNAS — enterprise storage built on FreeBSD.

BSD-origin tools that became universal:

  • libc implementations
  • make (BSD make)
  • diff, patch — essential to software development workflows
  • rc scripts — the ancestor of init systems

BSD contributed ideas that shaped how engineers think:

  • “Correctness over convenience.”
  • “Security as a design constraint, not an add-on.”
  • “Minimalism and clarity in code.”
  • “Stable interfaces matter.”

Linux culture often prioritizes velocity; BSD prioritizes durability.

BSD didn’t just give the world TCP/IP — it gave the world the shape of modern computing: sockets, filesystems, logging, containers, security tooling, DNS, routing, storage frameworks, and the OS foundations inside every iPhone and PlayStation.

24
-12
submitted 4 days ago* (last edited 4 days ago) by madthumbs@lemmy.world to c/linuxsucks@lemmy.world
 
 

Torvalds is confronting a reality where AI‑augmented code discovery, bug surfacing, and exploit generation are now part of the ecosystem he maintains. He's adapting because the kernel can't pretend these tools don't exist anymore.

For 3 decades, kernel development has been shaped by human‑found bugs, written patches, and human‑paced review cycles. Modern LLM‑based static analysis and fuzzing pipelines can surface hundreds of potential issues in minutes, generate PoCs for exploit chains, mutate inputs faster than syzkaller ever could, and find "weird machine" states humans wouldn't think to test.

-Torvalds can no longer ignore that.

Ignoring AI became impossible once it started surfacing kernel‑relevant bugs. For years, Torvalds dismissed AI codegen as "garbage", "dangerous", and "not helpful". -Then AI tools started finding UB patterns, surfacing concurrency hazards, generating syzkaller-style crash reproducers, identifying memory-safety regressions, and flagging suspious pointer lifetimes... he could no longer treat it as noise.

-Linus was late to the party.

The kernel community was moving on without him. Maintainers were discussing AI‑generated patch floods, new tooling to triage AI‑found issues, stricter patch acceptance rules, more emphasis on reproducible test cases, more skepticism toward AI‑assisted contributions, and more automation around review queues.

-He adapts when the ecosystem forces adaptation. -He's not a visionary

25
 
 

BSD has better security, load handling, network stack, documentation, cohesion, power efficiency, etc. -Try to explain why BSD isn't dominant on servers without mentioning the GNU/GPL cult.

Wasting 30-45% power isn't just about about laptops wasting power anymore, it's about datacenter‑scale inefficiency caused by architectural gaps in Linux’s power management stack.

CPU idle state handling is worse than Windows Server Linux often fails to enter the deepest C‑states under load patterns that Windows handles correctly.

  • Windows Server uses vendor‑tuned ACPI tables, DPTF, and firmware hooks
  • Linux relies on generic ACPI, often missing vendor‑specific power logic
  • Result: CPUs sit in C2/C3 instead of C6/C7, wasting 20–40% power

This is especially bad on:

  • Intel Xeon Scalable (Ice Lake, Sapphire Rapids)
  • AMD EPYC (Naples → Milan → Genoa)

Linux scheduler inefficiency The Completely Fair Scheduler (CFS) is great for fairness, terrible for power.

  • It spreads tasks across cores making more cores wake and using more power
  • Windows Server aggressively core‑packs workloads with fewer active cores and lower power draw

This alone can cause 15–25% power waste under mixed workloads.

PCIe ASPM is frequently disabled On servers, Linux often ships with:

  • ASPM off
  • L1 substates off
  • PCIe power gating off

Why?
Because vendors disable these features in firmware when Linux drivers don’t reliably support them.

That’s 5–10% wasted power across NICs, NVMe, HBAs, GPUs, accelerators.

Driver power gating is incomplete Windows drivers are vendor‑authored.
Linux drivers are:

  • reverse‑engineered
  • community‑maintained
  • missing proprietary power hooks

This affects:

  • Mellanox/ConnectX NICs
  • Intel i40e/ixgbe
  • AMDGPU/ROCm
  • NVIDIA (even with proprietary drivers)
  • NVMe controllers

Power gating gaps can add 10–20% inefficiency.

Kernel regressions are common and persistent A single kernel update can break:

  • idle states
  • turbo scaling
  • NUMA balancing
  • scheduler heuristics
  • cpufreq governors

These regressions often sit unfixed for months, especially in LTS kernels.

view more: next ›