FreeBSD, Who is it for?

very simple

if you have to answer with FreeBSD KDE, Gnome etc as a desktop/daily driver

who do you think it's the right candidate for FreeBSD?
[having mac os, windows and linux as an option too]

e.g
someone who does online banking, checking emails and cares about stability
 
This question cannot be answered in general, but for each person individually, only.
There are at least two short possible answers to this question in general:

1. (sounds a bit silly, precociously, but it's the shortest answer possible)
You need to find out yourself.

2. The question may be answered in reverse: (referring to "who do you think it's the right candidate for FreeBSD?")
Q: To whom is FreeBSD NO alternative? (The original Q of this topic)
A: For anybody who demands an operating system with the least personal effort at all
willing to pay the price by simply accepting and live unquestioning with what you're given.

Anything else needs more elaboration, from very personal points of view, which in any case only can be some kind of a guide that may give hints to everybody's own personal quest to find out themselves anyway.

A more comprehend answer you may get from e.g. :
HB, Chapter 1. Introduction
Explaining BSD
(I thought there was some article "To whom is FreeBSD, and to whom not" - but I cannot find it anymore; maybe was some introduction of a book?[help?])

Example:
someone who does online banking, checking emails and cares about stability
Those are all no issues to none of today's OS, even Windows by now is pretty stable
(Wanna hear old warstories from W95?😁 [We did not called it 'bluescreen of death'; too long, happened too often; it's just a 'bluescreen':cool:])
So decision's criteria need to be searched elsewhere; such as e.g. security, where IMO BSDs, then Linux were first choice.

It all depends on your (personal) needs, knowledge, expectations, demands, will to learn...
What is your task? What do you want to do with a computer?
Which software do you need? Certain apps depending on some certain OS? Or are you willing to try, explore, and learn openly, not only other software packages, but further more alternative working processes - other ways to do things?

To summarize it inconsideratly, unfair but most primitively simplified:
If most you want is to play games, consume media, or browse the internet with the least effort possible, use Windows.
If games are your third priority, or less, you can live with it takes some effort to get some run, many will not run satisfiably or at all, or - even better - you don't care about games at all, but you actually want to become really good at computers, I recommend FreeBSD.

With Windows you don't really learn much about computers. You learn Windows.
To actually learn about real computering you need to enter the world of computer science, which means unix[like], for which BSDs are (a bit) more genuine than Linux.
If you want to learn or do programming: unix[like]
Every unix[like] is a software development environment by its very nature. Maybe not a very good one at high end stage at vanilla installation, but they always come at least with a texteditor, a C compiler, and a programmable shell, plus lots of choices you may add ([almost] all [major/important] programming languages are available on [almost] all BSDs and Linuxes. [Don't start no beancounting on that here, please!])
Also a bit of programming is always part of any unix[like]; I don't talk software development, but small scripts to automate processes, deal with config files etc.
If you want to learn/do networking, servers, firewalls... unix[like]

For a start on unix[like] I recommend FreeBSD.
If you want to become some kind of hacker one day - whatever this means to you - you will get to other BSDs, and of course Linux, anway. But for the start I recommend FreeBSD. RELEASE, that's 14.2 at the moment; not 'CURRENT', not 'STABLE', not '15'... - RELEASE, installing all software by packages, only, not ports (except the kmod for the GPU to get a GUI). At least for the start, until you're quite well versed, know what you are doing, and why.
First be well-versed in moving self-confident within a house before start construction sites. 🤓

I hope I understood your question right, and gave you some useful answer.
 
i find if your stuck in no-mans land such as using a window manager GNOME applications conform well, whereas if you want to use for example KDEs FILE MANAGER theres conformance for whichever you may be choosing with it i think by default WindRiver was using KDE [or a window manager such as FVWM]... but now theres wayland and i personally because im an Xorg-Openbox enthuser i would prefer LabWc as a Wayland Window Manager...................
 
I would say, FreeBSD, NetBSD, OpenBSD, well *BSD in general, some more user friendly, some less are generally for people who are adventorious enough to try things out.
Like Michael W. Lucas said, it is definitely not for cuddling or hand holding.
Most Linux distros now, and Windows, and perhaps OSX ?, do a lot of handholding for you, abstracting the nitty gritty things what other call magic.
In *BSD you do or atleast should not have magic, expecting to do things on your own.
So, yes, I would aggree to NapoleonWils0n using the short form nerd.

Sorry if I sound harsh, but I do not think that FreeBSD is a OS for normies ?, if it is the right terminology.
I am not including you (OP) into that category, I am rather generalazing.
From my experience it is not something like if you want feature X, Y, chances are high that it is already available, packaged, etc... for you on *BSD. * = (Net, Free, Open)BSD.
But I can say, atleast FreeBSD makes hard stuff easy.
For example kernel compiling, building stuff from source, etc...
It is the case for me at least.
 
: D!~ i see that your saying i dont have an answer for..... i dont have one either! >.> looks at dell ... say for instance if it WOULD have worked maybe their referring to how it worked xthsaid changes ago ... here we go : hw.snd.basename_clone unknown oid, and SNDSTIOC_ADD_USER_DEVS error invalid arg now says could not create CUSE DSP DEVICE ok woah why did it just do it though i have /dev/dsp and /dev/dsp.ctl oh..am i like posting in the wrong thread :P
 
I would say, FreeBSD, NetBSD, OpenBSD, well *BSD in general, some more user friendly, some less are generally for people who are adventorious enough to try things out.
Like Michael W. Lucas said, it is definitely not for cuddling or hand holding.
Most Linux distros now, and Windows, and perhaps OSX ?, do a lot of handholding for you, abstracting the nitty gritty things what other call magic.
In *BSD you do or atleast should not have magic, expecting to do things on your own.
So, yes, I would aggree to NapoleonWils0n using the short form nerd.

Sorry if I sound harsh, but I do not think that FreeBSD is a OS for normies ?, if it is the right terminology.
I am not including you (OP) into that category, I am rather generalazing.
From my experience it is not something like if you want feature X, Y, chances are high that it is already available, packaged, etc... for you on *BSD. * = (Net, Free, Open)BSD.
But I can say, atleast FreeBSD makes hard stuff easy.
For example kernel compiling, building stuff from source, etc...
It is the case for me at least.
i for one can say #NETBSD is what i hear every person talking about IF they would ever is did i see it running at their house though? .... could the sound_server be working check PIDs for OSS ps -aux reveals virtual_oss -B -D /var/run/virtual_oss/dsp.pid -T /dev/sndstat -S -i 8 -C 2 -c 2 -r 48000 -b 24 -s 8.0ms -f /dev/dsp0 -c 2 -d dsp -t dsp.ctl is that bsd enough... then you test the stream with sox? and if it works pipe to py_http?: using lame:
 
i for one can say #NETBSD is what i hear every person talking about IF they would ever is did i see it running at their house though? .... could the sound_server be working check PIDs for OSS ps -aux reveals virtual_oss -B -D /var/run/virtual_oss/dsp.pid -T /dev/sndstat -S -i 8 -C 2 -c 2 -r 48000 -b 24 -s 8.0ms -f /dev/dsp0 -c 2 -d dsp -t dsp.ctl is that bsd enough... then you test the stream with sox? and if it works pipe to py_http?: using lame:
Lame does not fall into my category.
I am using FLAC mainly now.
Virtual OSS is well, to virtual for me, but I am running a sound server connected always to my heaphone input, waiting to plug in my headphones, and well...
But yes, judging from the commands, it is very BSD like.
 
People who want proper Unix, instead of an open source Windows clone.
Actually, I would not mind a windows clone, but getting better performance in Unix instead of a windows clone or windows itself is something where I could get a headache for 1-2 days setting program X, Y up for UnIx, and it would still be worth it.
 
Actually, I would not mind a windows clone, but getting better performance in Unix instead of a windows clone or windows itself is something where I could get a headache for 1-2 days setting program X, Y up for UnIx, and it would still be worth it.
i honestly thought this thread was my help topic i posted i said well wah they dont wrike mee! :(
 
someone who does online banking, checking emails and cares about stability
Im sure things like this does not care much about what OS you use as many Linux distros are stable including Arch.
From my point of view - Desktop is most important part after OS. I dont like DE i love WM`s only ... Qtile,i3,sway,awesome etc where real estate is important and multitasking is a life style.
But FreeBSD is one of those OS`ses where it has an Aura. You feel like this is it ! Plus - FreeBSD ( do not know how other *BSD based distros interacts ) is a bit more profesional in forums/reddits etc. than Linux distros :D
 
one SHOULD know though that FVWM was the window manager of choice which then they switched to KDE when the company offered PCBSD it was KDE
screenshot.png

so ok im up to the part where i dont have the related devfs files meaning virtual_devices but there IS a virtual device of vdsp just not vdsp0 vdsp1 in and out

**********Now they sponsor GhostBSD>?
 
Im sure things like this does not care much about what OS you use as many Linux distros are stable including Arch.
Partly, Arch is stable, if you update like every month, to get the bugs solved for some packages really quick.
I used Arch where I was between 19 and 24 years old.

From my point of view - Desktop is most important part after OS. I dont like DE i love WM`s only ... Qtile,i3,sway,awesome etc
I agree, the most hilarious part is, you need a terminal emulator anyway, being it a DE or WM so, why not use a WM instead ?

But FreeBSD is one of those OS`ses where it has an Aura. You feel like this is it ! Plus - FreeBSD ( do not know how other *BSD based distros interacts ) is a bit more profesional in forums/reddits etc. than Linux distros :D
You know, performance wise, it is the best I have ever experienced. No hiccups, no sound issues, hardware wise, and no handholding.
I can only thank Nvidia enough for natively supporting FreeBSD ,with AMD, probably I would be harder.
For example with Yuzu or Ryujinx, or Torzu, and what not.
Nvidia is compared to AMD better supported on FreeBSD.

Among other problems you do not have to check up the system if it misbehaves like SystemD with the many symlinks in Arch, or Artix with failing Firefox upgrades, where you upgrade from 132 to 80, because they had a problems.
I always do not understand Arch to force the user to check for systemDs carelesness creating symlinks and then decide 50/50 whether you should delete a symlink or not.
 
one SHOULD know though that FVWM was the window manager of choice which then they switched to KDE when the company offered PCBSD it was KDE
I heard that FVWM was discontinued, but I did not know why.
Well, money over money.
Another thing I noticed, is it Hatsune Miku Sama on the picture you posted ? <3
 
I heard that FVWM was discontinued, but I did not know why.
Well, money over money.
Another thing I noticed, is it Hatsune Miku Sama on the picture you posted ? <3
im just a petty scripter <- i can do things by see and sort of infer , if youve heard of android, dsdt, and macports i can go into a script program whatever it is look at something lets say a system update occurs and something doesnt work it asks conform function_a to method_a so you have to look at a new structure for code and ive taught myself to vaguely do code constructions
 
Actually, I would not mind a windows clone, but getting better performance in Unix
I understand Beastie7's post as it includes a cutting remark as a sidewipe at Linux turn-key distries.

But back to your post:
In my post I tried to point out there is a substantial core difference already between the both approaches of Unix and Windows.
Windows is a commercial product to be sold to as many customers as possible.
Unix is a philosophy of computer science about how operating systems have to be best from a scientific point of view, yet neither proved wrong, but so far true, only, nor something else was brought up so far proved being better. Which over the last fifty years produced a large tree of many OSs we call Unixes and unixlike, trying different approaches with individual interpretations of how strict this philosophy has to be followed, which in my eyes was more the BSDs, and compromises need to be done with other OS, which in my eyes was more Linux, while as always in nature it gets harder to draw a clearly discriminating line the closer you look.

Understanding both of those brings complete different, even contradicting ideas about OSs.
The missing performance you may miss with unixlikes comes from the compromises made to have priority on other, some may say more important things.
The performance issues mostly criticized are games, and WLAN. Right? Cross your heart! And well, yes, when start to count beans you find others, too, but you also find several things where (Free)BSD(s) or Linuxes perform better than Windows.
The first is top priority for consumer machines, but of minor value within a scientific context, or professional machines. As I also tried to point out in my first post: It all depends on what you want, need, expect.

The second one was of minor value until more and more users switched to mobile computing as their primary, or even only driver. To me that's no real issue. To me a laptop still is a secondary machine, a sidekick. I use it when I travel, only. And I don't travel much. My main driver consists of several, individual, exchangeable modules assembled within a big tower, four monitors, and good, real keyboard; unmobile, having a LAN cable.
But as far as I picked it up, FeeBSD developers are working on that with high priority and already made some progress.

So, bottom line: As long as there is nothing being best at everything - which is one of humans oldest longings, always a good dream lots of crap is sold with, but by nature simply impossible - you always have to make compromises, which requires personal effort to think about yourself what you need, see what you can get, and decide which satisfies you most while understanding there is and never will be anything that satisfies you completely.
That's life, that's nature. It will always be so and never change, no matter what sellers tell you.

I heard that FVWM was discontinued, but I did not know why.
It is. There is FVWM3, last update released 11/24.
But I still run the predecessor: fvwm-2.6.9_4 Which is not "continued" anymore. It reached its maximal peak of mature. It's sophisticated, finished programmed, no need to add anything anymore. :cool:
I don't care if it's not "continued." Why? It's there. It worx for me. It does its job. It satisfies me. That's all I need. Hey, get this: I am actually using a window manager that has seen his last update 2016 - 9 years ago! - and is based on FVWM1, which is from 1993, over 30 years old, and yet my machine still runs rock solid, I never saw weird behaviour, neither was hacked, nor fell apart, nor catched fire,... 😁
Disagree - Gentoo, Arch, nixOS - these are for nerds tooo.
To me the prototype of the typical Linux nerd is someone who do not actually use his computer, but thinks he's a hacker, because spends most of his time to customize his machine and try to reinstall all the apps being broken by lost dependencies from the last update, and is very unhappy if he has a rock solid running machine for more than two days, because then he gets bored, and is happy if there is an update that breaks dependencies again, so he finally has something to do with his computer. Otherwise I have no clue why so many people here on FreeBSD run CURRENT, STABLE instead of RELEASE. Must be some habit they brought from Linux.
My theorie: May be because it's too boring. If it runs rock solid, they have no idea what to do the machine. 'cause that's what you get with RELEASE: An almost always rock solid machine; broken dependencies are seldom. You'd need to think of what you actually need a computer for, and, worse, actually need to start to do something real with it. 😁
 
The performance issues mostly criticized are games, and WLAN. Right?
Well, games fall into the performance issue category, but I do not know about WLAN, because I am using LAN.
For me personally, I get better emulator performance on FreeBSD than I do it on minimal linux distros or Windows.
I guess it has something to do with the CPU task scheduler.
Windows in this case cannot hold 4.4 GHz on my Zen 5 CPU, and jumps like crazy between clocks, although I have performance mode enabled.
FreeBSD seems to run at 4.4 GHz constantly.

To me the prototype of the typical Linux nerd is someone who do not actually use his computer, but thinks he's a hacker, because spends most of his time to customize his machine and try to reinstall all the apps being broken by lost dependencies from the last update, and is very unhappy if he has a rock solid running machine for more than two days, because then he gets bored, and is happy if there is an update that breaks dependencies again, so he finally has something to do with his computer. Otherwise I have no clue why so many people here on FreeBSD run CURRENT, STABLE instead of RELEASE. Must be some habit they brought from Linux.
My theorie: May be because it's too boring. If it runs rock solid, they have no idea what to do the machine. 'cause that's what you get with RELEASE: An almost always rock solid machine; broken dependencies are seldom. You'd need to think of what you actually need a computer for, and, worse, actually need to start to do something real with it. 😁
I actually read that if you do pkg installs from from the official fresh ports, then you can also get pkgs with broken/lost dependencies, but if you are updating ports, and the building from ports, then that issue is reduced, not present at all ?
I never had problems with ports building so far, but I remember compiling sway 1.9 back then, vs the pre-build sway 1.9.
The compiled one had a updated wlroots, which the pre-build one lacked.

I am running RELEASE all the time, and if I need feature X,Y,Z from current, or stable, I just patch it in, minimizing breaks, while getting some latest features.

Actually it is quite nice to have a computer which works for you, and not against you so, you can move forward with plans/ideas, and are not bound to fixing, and fixing again things, which should not be broken in the first place.
 
I have had great success these last few months moving a bunch of old candy cab set-ups over to FreeBSD. They were all running some form of Windows (mostly 98 - 7 and CE) because Windows was required to support the software (games) those arcade cabinets were running. I have multiple systems that require a hodgepodge of patches and hard to find drivers to run the games on them that would regularly crash and require total re-install at least once every 2 years or so. I don't understand why you can't simply leave Windows alone but it always seems to find a way to eat itself for no reason. This shouldn't be happening since these machines at not connected to any network and aren't being used for anything but booting into one application (or a small loader for a handful of applications) but at least once or twice a year one of them would die for non-hardware related reasons.

So far I've moved over two cabinets with plans to move over 10 more to FreeBSD in the near future. The two I'm doing testing on require the ability to run a wide variety of Windows 32-bit and 64-bit, MS-DOS and PC-98 software. Most of the software isn't intended for general purpose Windows installations either. A lot of it was intended to run on non-standard PCs or PCBs that ran some form of Windows CE or NT. Or custom versions of DOS. Thus they required all sorts of patches, hacks and third party software to fool the games into playing nice with common hardware. I've wasted many hours of my time tracking down instructions littered with Kanji I had to look up and trolling through old archives to get patches to make the games run on the GPU or work with my standard Sanwa joysticks and buttons.

It's a real cluster fuck in other words. Especially when game A expects some old Nivida GPU and game B wants an old AMD GPU and neither will work on a model of either company's GPU that was released 6 months after it came out. Never mind making a bunch of those old PC-98 games work on anything that isn't a 40 year old system or tracking down (or writing) some obscure emulator to make software that was written for hardware that was never documented work.

Originally, I planned to attempt this with Linux (Gentoo in particular since I know it well) but for various reasons Linux wasn't an ideal option for the OS on these machines. I needed something stable that didn't move as fast. A simple OS that I could set-up, forget about and then return to years from now and still be able to understand. FreeBSD was the natural choice. Since it has VMs out of the box, a pretty recent port of wine and any emulator that hasn't been ported can be run through the Linux emulation layer or wine when needed.

Since most of these games aren't that hard on the CPU/GPUs any loss in performance (which I haven't noticed anyway) isn't a big deal. 90% of the games I've tried worked pretty much right away. The other 10% will probably work once I get the time to go through figuring out what patches they need again. As I go through this process I'm documenting it since a lot of this stuff has never been documented and the little that has is being quickly loss to time as older websites go offline.

In due time I'll probably even feel confident enough to hook these back up to the network and maybe give them access to the internet. They'll be behind a firewall of course. But it'd be nice to emulate some of that old networking stuff for these games (leader boards and such).

FreeBSD is for the arcades I reckon. At least for ours. It's a shame we can't share. I'd love to package some of this stuff up. But it'd be impossible to get the rights to do it and most of these people aren't even alive anymore or they released their software anonymously 20+ years ago. Also I'll be honest we're not supposed to have copies of a lot of this stuff anyway. A lot of it got dumped by arcade owners years ago and a bunch of us would share with each other and attempt to run this stuff on standard PCs just to see if it could be done. We had a nice little community for a long time until the Japanese caught wind of our activity and had it all shut down. A few are still doing it but most of the people involved moved on a long time ago. I personally don't see anything wrong with sharing a 15-35+ year old game that you can't even legally buy anymore with a few other arcade nerds on the internet. But the people that robbed the creators of the IP rights don't feel the same way about it.

At this point I keep doing it because we've already saved a lot of 'lost media' and I enjoy playing them from time to time. The people that come over like playing them too. If it weren't for the efforts of a bunch of arcade owners over the last several decades we wouldn't even have the ability to play these games anymore. Since a lot of them got very limited releases and all the old machines have either been destroyed or there is only 1-3 left sitting in the back of a musume somewhere. A lot of this software has not and will never be ported to a modern console or PC even though they're squatting on the IP and refuse to let anyone else buy it. Most of the source code for this stuff was lost long ago so the only way to play them is either finding and repairing the old hardware (which can cost $50k+ or more in some cases) or figuring out a way to patch the binary to make it run on a different system. Even the stuff that was made for the standard PC in their time are very rare and no known copies exist anymore. Since a lot them were one-off projects done by one guy that only sold a few copies of it at a convention.

FreeBSD is just about the best OS around now if you're interested in running old obscure binaries for most systems that were in common use between the early 1980s and the mid 2000s. Linux is decent at it as well. But it's much harder to set all of it up and keep it running. Especially when they seem hell bent on breaking everything in userspace every couple of years now. The kernel might not break userspace but the people writing userspace software certainly do as often as possible. Plus they don't really focus on my own use cases anymore. Linux is targetted more at corperate desktops and servers now and not the little guy that likes to mess around and hack on stuff. I suppose the same is true of most of the *BSDs to. But at least they don't move as fast and offer an actual full fledged OS/base system instead of throwing together a bunch of unrelated projects and trying to tie them together with a mountain of garbage.
 
I don't understand why you can't simply leave Windows alone but it always seems to find a way to eat itself for no reason. This shouldn't be happening since these machines at not connected to any network and aren't being used for anything but booting into one application (or a small loader for a handful of applications) but at least once or twice a year one of them would die for non-hardware related reasons.
A friend of mine said, DEs are designed to get slower and slower by time, but I do not know whether he is right, or not.
I think backdoors in Windows, and stupid registry editing, make the system slower, and introduce bugs which crash the system, among updates which should well, make the system better, and not worsen it.
Are windows updates actually installed without you requiring to have a internet connection ?

I've wasted many hours of my time tracking down instructions littered with Kanji I had to look up and trolling through old archives to get patches to make the games run on the GPU or work with my standard Sanwa joysticks and buttons.
I see, Kanjis.
I am very fluent in Japanese so, if you have something you want translated, you can ask me.

Since it has VMs out of the box, a pretty recent port of wine and any emulator that hasn't been ported can be run through the Linux emulation layer or wine when needed.
I have not tried it, but can Ryujinx run through linuxulator without having something like a linux environment set up, or wine ?

A lot of this software has not and will never be ported to a modern console or PC even though they're squatting on the IP and refuse to let anyone else buy it.
What about decompiling the binaries ?
Frankly speaking, I do not know how hard it could be, but there are a lot of references.
The Legend Of Zelda Ocarina of Time got decompiled, Super Mario 64, too.

Even the stuff that was made for the standard PC in their time are very rare and no known copies exist anymore.
I do not know if I can say it on this forum, but maybe the TOR browser could help.

FreeBSD is just about the best OS around now if you're interested in running old obscure binaries for most systems that were in common use between the early 1980s and the mid 2000s.
It is also the best OS if you want to play Windows games through wine.
Usually the GPU is better used than on Linux or Windows, CPU is also better used, at least better than it is the case on Windows (AMD Zen4, Zen5).
There are only two downsides, though.
1) Nvidia GPUs are 100% supported through the publisher, I am not sure if AMD GPUs are also as well supported driver-wise on FreeBSD.
2) The game needs to work. If it does not work you can either fix it, or give up, but if you fix it, it will get a nice FPS boost.

Linux is decent at it as well. But it's much harder to set all of it up and keep it running. Especially when they seem hell bent on breaking everything in userspace every couple of years now. The kernel might not break userspace but the people writing userspace software certainly do as often as possible.
That is the problem with Linux.
I think void-linux tries, or tried to get a stable userspace by updating carefully and not on every occasion.
Their approach worked, but one problem that they have is broken software.
Transmission-CLI for example had a man page, but the binary was broken.
You could start it as a daemon for runit, but you could not issue commands...

Linux is targetted more at corperate desktops and servers now and not the little guy that likes to mess around and hack on stuff. I suppose the same is true of most of the *BSDs to.
Well, I think Linus stated something like he does not care about desktops, but is only focused on the server side ?
I cannot say whether it is true or not, but I think that FreeBSD in this regard is very open.
They do what they want to do without having a corporation as a target, and a clear focus on networking, internet, and other related things.
I also read that one developer stated that not corporations nor the FreeBSD Foundation decides the future of FreeBSD, but the group maintaining and developing it, does decide it.

As for OpenBSD, is it not something like a "One man decision + followers" kind of thing ?
In contrast to FreeBSD where you have a group so, the exact opposite.
I believe their goal is just security in every aspect, but I have not gotten enough into OpenBSD to be able to say something more concrete.

I do not know which stance NetBSD takes, but it seems to be a good alternative to FreeBSD, eventually ?
FreeBSD has indeed a large userbase compared to other BSDs, and have great software at least to start things.

But at least they don't move as fast and offer an actual full fledged OS/base system instead of throwing together a bunch of unrelated projects and trying to tie them together with a mountain of garbage.
Even if they move, they have options for staying compatible with older FreeBSD versions, I believe from FreeBSD 5 onwards ?
Well, throwing together random things, and calling it an OS will never go well...
 
Im sure things like this does not care much about what OS you use as many Linux distros are stable including Arch.
From my point of view - Desktop is most important part after OS. I dont like DE i love WM`s only ... Qtile,i3,sway,awesome etc where real estate is important and multitasking is a life style.
But FreeBSD is one of those OS`ses where it has an Aura. You feel like this is it ! Plus - FreeBSD ( do not know how other *BSD based distros interacts ) is a bit more profesional in forums/reddits etc. than Linux distros :D
totally agree
 
Back
Top