51–57 of 57 posts
Earlier quoted context omitted.
FreeBSD has supported containers since the 90s.
And it has 5-6 different ways for managing jails, some of them abandoned, others peculiar, and some recently degrading in quality.
Earlier quoted context omitted.
Isn't Android plagued by all manner of proprietary dependencies for hardware support? I don't understand all of the pressures on vendors in the Linux case, but at least one of them is that they can't upstream their drivers (and thus unload some of their maintenance burden on the Linux kernel team) unless they license them in a way that's considered suitable by upstream. If they don't do that, they're more likely to b…
> . If they don't do that, they're more likely to be broken by Linux changes, and it makes distributing their drivers more annoying So the idea is that having no drivers is better than having proprietary drivers? Seems like a perfectly reasonable and sensible approach..
It's also more or less a given that first-party code will be better-integrated into an OS than third-party code is. That was a prevailing element of the discourse surrounding the outage CrowdStrike induced on Windows weeks ago, for instance. That's not a proposition unique to open-source operating systems. Indeed, what is unique to open-source is that is possible for outside vendors (or individuals) to put their code through a process that eventually gets it that maximal level of integration.
So, uh... no?
As a long term FreeBSD user (since 2.0) and advocate, my view is that FreeBSD should focus on its niche as a rock-solid server operating system. For most developers buying a MacBook and SSH-ing into a server is probably the right answer (or running a VM if you really need something local). The level of effort to match the MacBook user experience feels like a lost cause (Linux has been trying to do this for decades wi…
I agree, we often overlook the fact that virtualization made enormous progress in the last decades on consumer hardware.
So if I want to run FreeBSD on my laptop I might have to boot Linux first (I know...). Simply because few OS can afford the luxury of broad hardware support nowadays.
FreeBSD is still a very competitive OS but it might start lagging is some aspects behind the most innovative Linux distributions such as NixOS.
My wish would be some work on configuration management and automation since it might be a low hanging fruit for such an integrated OS developed by a single entity.
I think that a major problem is that you can't legally force vendors to open source the drivers they distribute. Most importantly wifi drivers which are critical to making an operating system that people can actually use.
For the last 5 years, I have replaced FreeBSD on servers with Linux. The main reason is that Linux, is a lot less work. The time spent on upgrading for example Debian is significantly less than FreeBSD which has a cumbersome process which requires some manual human interaction a few times during the process. Another thing is that behaviour of some applications I write are different on FreeBSD compared to Linux. One p…
Switching (back) from om Mac to Linux, I can definitely say that the painful experience was with the Mac, I just got used to it along the years. The Plasma desktop is now a breeze (literally ;-)). Battery is surprisingly long lasting, too (7 year old Thinkpad X1, easily 7-8h of battery). It just works.
Earlier quoted context omitted.
Switching (back) from om Mac to Linux, I can definitely say that the painful experience was with the Mac, I just got used to it along the years. The Plasma desktop is now a breeze (literally ;-)). Battery is surprisingly long lasting, too (7 year old Thinkpad X1, easily 7-8h of battery). It just works.
Out of curiosity, which flavour of Linux are you running?
I could be alone in this, but I think getting containers (OCI, Docker) running on FreeBSD seems like a better direction - I totally get that Docker is a Linux kernel thing but the idea of a file system with layers, registries etc could be a thing right? I love FreeBSD but cannot really use it in a production environment until I can deploy containers on it as that is pretty much the defacto for our workflow. Maybe it…