this post was submitted on 12 May 2024
375 points (97.0% liked)
linuxmemes
21226 readers
37 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
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
I personally have tried FreeBSD and some FreeBSD "distros" on the desktop, and have used *BSD-based stuff as servers/single-purpose machines.
As a desktop system (user-centric use case), you notice how hardware support is sometimes problematic, especially on laptops. I personally had problems with NVIDIA GPUs, already a problem on Linux, being a big problem here as well, and don't mention WiFi (FreeBSD doesn't support 802.11ac and up currently) or Bluetooth. Software-wise, if your applications do not have a *BSD version, well, then you are relying on Linux ports, which for desktop use isn't exactly great.
But, in servers/headless setups, *BSDs are shining, with the most important things running rock-solid, stable and resource-friendly.