To this day I admire Linux for having the grit and perseverance of maintaining ext2, ext3 and ext4 as separate code bases for so long. Equivalent FreeBSD UFS, UFS with soft updates and UFS with journaling is one code base with each generation as a backward compatible feature. Given FreeBSD's negligible market share perhaps worse is indeed better.
FreeBSD usage is mostly hidden behind very large storage environments. Think PB scale HPC and NetApp (the glorified FreeBSD with some sellable added complexity), all running FreeBSD at it's core.
huh, does that explain why the PS5, in 2023, still gets really upset about having power yanked while it’s not turned all the way off? It yells at you (talk to PG&E, Sony) and does a slow fsck when power is restored. Being stuck with old FreeBSD FFS would explain it. You’d think they could invest in a modern filesystem to make this headache go away.
Good license with a bad product is still bad, so there must be more the "just" the license. For example netflix, they could use linux without any problems (since they don't redistribute the code nor the appliances).
>Plus they also ship devices with Netflix code on them.
Are you talking about open-connect? They don't ship that to "End-users", and you can sell an appliances with GPL software and proprietary code on it..hello Android?? And please stop now, your arguments are like from a 12yo, and i know for a fact that your much much older, also sometimes wiser, i don't know why that is not available for you today.
What BS? The amount of precious upstream changes that FreeBSD gets from all vendors shipping their code?
Android is actually a good example, it is no accident that Google has been cleaning Android from GPL code, leaving only the kernel and since Android 8 only Project Treble drivers (out of kernel) are used.
Fuchsia is even better, only Apache and MIT licenses.
