The Linux way of doing things sounds great, as you can use whatever combination of tools you like. However, developers don't always share the same goals when designing their programs. This can lead to tools needlessly increasing in scope, like systemd.
Post by twetch#1927
What you can and often do end up having with GNU/Linux is a system filled with tools that overlap in features, causing redundancy and therefore bloat. A complete departure from the Unix philosophy of designing programs that "do one thing and do it well."
What the chain says
- Block
- 631 166
- Time
- 2020-04-18T16:43:50Z
- Signer
- 1MfKwvZTcc89ZPGypu1z7upQu8LjKYvUzL
- App
- twetch
- Type
- post
- Content type
- text/plain
- Name in tx
- twetch#1927
Fields the transaction did not carry are omitted. Open the payload to see the bytes as stored.
Signed by
1MfKwvZTcc89ZPGypu1z7upQu8LjKYvUzL VerifiedReplies (6)
BSD systems are different however, as the kernel and userland/core utilities are developed and maintained in-house by the same team. This means the goals of the developers are aligned, allowing for the system to be kept as small and simple as possible.
As for the actual systems themselves, I tried OpenBSD first. The installation was a breeze, however post-install setup was more difficult than I'm used to. I had some driver issues and no 3D acceleration, so videos and web browsing were unbearably slow.
Frustrated with the performance and lack of support, I tried FreeBSD instead. The installation went even smoother than OpenBSD. WiFi worked out of the box, and the OS was using 8mb of RAM at idle with no GUI. For me, this was like something out of a dream.
With a minimal i3wm GUI set up, my memory usage SKYROCKETED to a whopping 70mb! In this state, the system had about 200 packages installed, compared to Ubuntu's ~1800 packages or so for a default installation. At this point the benefits were obvious to me.