FreeBSD is a complete OS, while debian is a distro, i.e the Linux kernel + a lot of programs including the utilities from GNU. So almost everything in debian comes from a package while in the BSD world, there's a split between the system utilities (called base) and the third-party projects (called ports). The port system itself is a collection of recipes to build those projects.
But the nicest thing about the software in the base is that they are developed in sync with the OS, so their code can be simpler.
FreeBSD ports are more up to date. Debian packages are famously out of date - their claim to fame is stability not staying up to date. Arch is a better comparison here if you care about this you would be asking about Arch not Debian: that you are asking about Debian implies you want this out of date.
The other major difference is FreeBSD ports lets you chose the build options - the defaults are normally good, but if you don't like how Debian (Arch...) choose to build your packages you are not stuck. Ports even mixes with binary packages so you can choose the defaults for some things and build others yourself and the system will track everything and when things need to be updated. This is something you rarely need, but when you do FreeBSD soundly beats everyone else just because the effort is so much less (again though, most people never need this in the first place - and Debian has pushed less need of this on applications which is a good thing)
Ports is a meta build system, from which packages are created. Gives a lot of convenient power and flexibility. For ready built packages, the FreeBSD equivalent of dpkg or whatever five different package commands Debian is using now would be pkg.
PF seems to me like pretty much the most well regarded firewall there is -
with a nice, sensible DSL for config. If you don't like like it, you can use use IPFW or IPFILTER, which are alternative, built-in, firewall front-ends.
- In the end, it was just too much having to re-invent the wheel for common server tasks
Maybe you have built your routine around a system that have reinvented the wheel? I think FreeBSD knowledge degrades more slowly than that of Linux distros.
- I'm just not an OS dev.
That's how I feel when I enter the chaotic Linux world. Do you think my life revolve around keeping up with this shit? :)
> That's how I feel when I enter the chaotic Linux world.
I feel that as a Linux user. I really like Linux, I use it on my desktop and it runs all my servers. Delving into forum posts to find some solution to a specific problem can be exhausting. Sometimes you get a top result from like 2011 and it is out of date so you then need to spend X minutes trying to look up something more recent.
You haven't really gone 'round the block in the world of quasi-modern Linux until you're Googling for answers and guidance to what seems like some obscure issue, wherein: The noise is intense and replete with bad answers, unanswered questions, lack of report (positive? negative? how 'bout "none"?), and dumb SEO spam.
Time passes (how much time? are the birds singing yet?) as you keep slogging through that endless sea of muck.
Finally, you run across an old post on some forum where the person not only wrote about the problem, but also the cause of the problem -- and the answer.
So you're reading along, working to once again evaluate whether your problem matches their problem. And the more you read, the more familiar it all seems... like you've been there before.
"It can't be," you say to yourself.
But you scroll back up to the top of the comment and look at the author's name anyway.
And yep, sure as anything: It was you. Six years ago, you wrote about that exact problem yourself and posted a perfectly-cromulent solution to it.
So you fix it (again), note that the birds are in fact singing, and to try to sleep for a bit while pondering your life's choices: You could have found a hobby in origami or perhaps woodworking. Maybe worked as a Mennonite tradesman producing leather goods, or as a carpenter (even an Amish one if any of that seemed too high-tech).
But you didn't. You chose this path instead. It could have all been so simple, but it isn't.
Addendum:
I've used FreeBSD as my daily driver (I hate that term) since around 2004. Including through cs/math university. With Windows in a VM for "I need it".
The longer I've used it the more I'm annoyed by the trivialities of Linux distro management. And the bugs that happens between ill fitting parts composed by underfunded distro developers.
And I didn't mean to imply that FreeBSD is stale. There is big stuff happening continuously. Right now it's compatibility with Linux Wifi drivers, which will make FreeBSD more laptop-able. And pkgbase, which brings some of the compile-your-self flexibility of FreeBSD to binary management, and merges the two tools that decides what makes up your system into one. And kinda makes FreeBSD into the slim system that people already claims it to be.
My pet conspiracy is that pkgbase happened because the powers that be didn't want the 1000 battles to remove junk. Any time anyone wants to remove something there's always one or two guys on the mailing list claiming their livelihood depends on not having to do "pkg install Ø". With pkgbase its all gone.
They might've been trying freebsd back when pf wasn't well supported. Back when I last used openbsd (which might be nearly 20yrs ago now - eek), pf support on freebsd was lagging quite a bit.
Not sure what things are like now though - I'm guessing it's much better as pf was obviously the best option :)
I don't need more movies. I want higher quality movies. And I don't think AI will work out any better for movies than it does for youtube documentaries. It's getting tiresome to find anything worth watching among all the slop.
This is like saying it's a bad thing that phone cameras are getting so good because expensive cameras were keeping out the garbage films.
Expensive cameras are still better. And yet, it's good that people who were never going to be able to afford those cameras have something else they can use to tell their story.
Mollusc is a perfectly legal way of writing mollusk if that's what you mean. And everyone knows that whales evolved from hungry beach snails around 50mya.
It's far more active than redox and it's actually running on real consumer devices. There are more than a hundred monthly active committers on the repo you were looking at, and that's not the only repo fuchsia has. Calling it dead or prone to dying is simply not based on any objective reality.
Okay, I take that back. Maybe I shouldn't say it is dead, but it is more on life support, where there is no new features being developed. Simply put, it is dead to me not that the project ceased to function, but dead to me in the sense that it is out of relevancy, just like Hong Kong.
What are the 100+ daily commits doing if not adding new features? Google is not spending any effort marketing the roadmap for the project, but it's very much still alive and in active development. There are RFCs published fairly often about technical designs for various problems being solved and you can see lots of technical discussions happening via code review.
Some new things that I can think of off the top of my head:
* More complete support for linux emulation via starnix.
* Support for system power management
* Many internal platform improvements including a completely overhauled logging system that uses shared memory rather than sockets
Most project happenings are not that interesting to the average person because operating system improvements are generally boring, at least at the layers fuchsia primarily focuses on. If you've worked in the OS space, a lot of things fuchsia is doing is really cool though.
Birds of Parallax from 9:45 onwards is my favorite.
They had this on repeat in an electronic music history exhibition I attended in a London museum some ... counting... 12 years ago.
* Ease of management - more holistically designed.
* Rock solid parts that fits together - more holistically designed.
* ZFS, jails, bhyve, dtrace, ports.
* If it works today, it works tomorrow.
* A more approachable community (which AMD says is the reason why they are developing for FreeBSD before Linux now).
* Transparency and simplicity of how it works - if you can understand it, you can manage it and fix it.
* Documentation.
* Fun! Linux is not fun.