3 ms·
I worked in IT for 20+ years too, so you do need to flaunt your experience around. Yeah, well, this is why you have 2 year update cycle, like Ubuntu, Debian or
by SomeoneFromCA 3y ago
I worked in IT for 20+ years too, so you do need to flaunt your experience around.
Yeah, well, this is why you have 2 year update cycle, like Ubuntu, Debian or you have overlapping support periods like Redhat. You can update you system every once in a while, you know beforehand what will be in the next release and when it will happen. Not some insanity of rolling or semi-rolling packages like BSDs have.
Yes, security updates are always a lot less risky than quarterly FreeBSD updates. Quarterly does not receive all sec updates anyway, but do receive some. Worst of both worlds.
In fact I think, FreeBSD is not suitable for majority server purposes exactly due to terrible support cycle, despite clear technological advantages (ZFS, Jails etc.). If you limit yourself to some narrow uses, completely serviced
by the base system, then yeah you may use it as server, but that is very niche use.
FreeBSD actually is a good replacement for Arch-like systems, for workstation uses, exactly due to its semi-rolling nature and separate base systems, this will cause less breakage compared to Arch.
- BSDobelix 3y agoYou still don't understand what i meant. Breakage means you have not tested anything, it's your fault and your responsibility. To stay near upstream is incredible healthy, software stacks are a living thing and should be treated like that, remember the Mainframe trap? FreeBSD supports for example Java8, PostgreSQL12 and GCC4.8. The port-tree has not just the latest upstream version available. And why would i want a Red-hat-patched 6 y/o Nginx on my machine? No thanks. >Yes, security updates are always a lot less risky than quarterly FreeBSD updates Let's stop here when you start comparing apple with oranges.