It's not really a demerit of FreeBSD given their lesser resources (and even less vender support) than Linux.
Most of the major ethernet chipsets for networking you'd expect to find in a server are well supported and the system is quite solid for many server use cases, but you're probably not going to be running bleeding edge consumer hardware day one on it.
On the desktop side of things Linux has far superior hardware support for current GPUs/Wifi chipsets. AMDGPU support is a few card generations behind (they have to spend effort porting from the Linux drivers) and things are still mostly in X11 land and you don't have Valve supporting gaming on BSD.
I'd still be interested in running FreeBSD on severs, it just takes a bit of different knowledge (the handbook is excellent) and with OpenZFS being a thing on Linux there's not as much exclusive to the BSDs on a surface level that Linux can't at least mostly provide.
Always a possibility with any distro, but the tooling around it is flexible and repeatable. If another group of people wanted to continue off where they left off it would be far more possible than a lot of the Ubuntu forks.
Just need the Atomic Fedora base to still be around and everything else is already pre-setup to run on GitHub infrastructure neither of which I anticipate going away soon. (Famous last words)
Calling it a superset of Fedora rather than just being its own bespoke distro can be a fine line, but really there's nothing stopping anyone from forking it and continuing on, a good few people run their own forks already to meet their own needs a bit more specifically.
I'm CS new grad looking for entry to mid level positions to gain industry experience.
Full-stack experience with building backend APIs in Java and Golang, and frontend interfaces with Astro and React. I'm a Linux enthusiast with a fair bit of systems administration knowledge as well.
Familiar with dealing with VoIP/messaging platforms such as Discord and Mumble.
From a marketing perspective perhaps, but it's still a supported LTS release of Ubuntu at heart and having two different version numbers would create ambiguity.
Things that should work on that particular Ubuntu LTS should work in Pop_OS! And at least you don't have to cross reference things.
Thankfully they keep important things more up to date with newer kernels/hardware support than the version numbers would suggest, but I think that it's a common point of confusion.
>I gather that having the games installed somewhere outside of steam's /home/ directory was not jiving with flatpak's security model. It took some non-trivial editing (thanks, flatseal) to finally let the Steam flatpak be able to write outside of its own directory and install the games.
I think flatpak could use a built in notification method of some sort to add exceptions to paths it's allowing access to, though I imagine it would still require effort on the application's part which maybe would never happen (especially with steam using its own custom file browser)
>At last check in, I still can't launch CS:Go, because of some backend problem while trying to play the opening movie
I've had no such issue (and it's worth noting the -novid launch option), but regardless valve still treats Linux as a second class platform despite the steam deck which is fairly disappointing.
The issue I do have is that the new overlay will crash cs:go in openGL mode and Vulkan mode has massive stutters.
I'm optimistic CS2 will be better, but to be determined.
Feigned certainty is often a indication of the opposite. In many cases people just absorb someone else's opinion on topics just in an effort to feel informed.
I'm not going to say I'm never guilty of it myself, but often asking even for the slightest bit of further explanation collapses that or otherwise just leads to repetition.
>How do I know that the Samsung DNS servers are being blocked?
Would have to know all of the domains that the TV connects through, that they're in one of pihole's blocklists, and the TV actually respects the DNS setting entirely and doesn't have any hard coded IP addresses
>What prevents Samsung from registering new meaningless-sounding DNS names and continually pushing out TV software updates peddling “Security and bugfix” release notes?
Nothing.
The real solution is to not connect any smart devices (especially stuff like TVs) to the internet as most are inherently untrustworthy.
Maybe a whitelisting system on a firewall would be more appropriate than a blacklisting system on something like pihole.
Most of the major ethernet chipsets for networking you'd expect to find in a server are well supported and the system is quite solid for many server use cases, but you're probably not going to be running bleeding edge consumer hardware day one on it.
On the desktop side of things Linux has far superior hardware support for current GPUs/Wifi chipsets. AMDGPU support is a few card generations behind (they have to spend effort porting from the Linux drivers) and things are still mostly in X11 land and you don't have Valve supporting gaming on BSD.
I'd still be interested in running FreeBSD on severs, it just takes a bit of different knowledge (the handbook is excellent) and with OpenZFS being a thing on Linux there's not as much exclusive to the BSDs on a surface level that Linux can't at least mostly provide.