Why did you stopped using FreeBSD ?

Cthulhux said:
I stopped using and contributing to FreeBSD when they embraced the toxic SJW community. Not looking back ever since.
Previous discussion.
Click to expand...

I don't believe much in "communities." If OpenBSD had support for Bluetooth, I'd think about using it, but my speakers and earphones are wireless because I like to avoid cords, so I cannot use OpenBSD.

Perhaps OpenBSD avoids Bluetooth because it's an unsafe technology (I'm not sure), but I still rather use it than having more cords around.

FreeBSD works very well. Its performance is excellent. My computer feels like new since I installed it.

You cannot expect everyone in a "community" to think like you. And you can always expect some people (especially administrators and people up the hierarchy) to behave as little tyrants. That's why I don't like any community. But I'm afraid it happens mostly anywhere. I can tell because my opinions don't align with any mainstream stance; I have my own set of values, so everyone tends to end up disliking me.

Anyhow, thank you for contributing to the FreeBSD forum.
 
recluce said:
Did you ever consider that -CURRENT might not be for you? It is kind of supposed to drive you nuts, especially in early days (i.e. far from next release date) where there is lots of instability. You might want to track -STABLE instead or -RELEASE.

Hint: while you only need to update the boot loader for every minor release with -RELEASE and -STABLE, I would do this with every update of base on -CURRENT. It is merely copying one file, if you are on UEFI boot.
Click to expand...
You should read my posts before quoting me... I've been tracking -STABLE for months and I tried -CURRENT just to check if the bug I'm experiencing (which BTW is a regression from 14.x) was solved by accident.
 
Mostly unsupported hardware(network card firmware and driver) and i didn't figure out how to dual-boot with windows and i wasn't a fan of daily driving a virtual machine.
it will be cool one day to contribute to freebsd drivers though.
 
Don't want to stir up any trouble, but as I wasn't interested in "SJW" stuff at all when it happened back in 2018 I just now gather all the code of conduct affair details, including the OpenBSD shilling and such.

Well right now, a lot of people that said farewell in that thread are still here, our code-of-conduct right now is LLVM one and very no-nonsense, corporations haven't turned FreeBSD into MacOS, and every time Apple, Microsoft or Linux distros do a stupid thing we get scores of people being interested to cross over to FreeBSD side.

Btw...in risk of inflaming some random unsuspecting member, but people insisting OpenBSD is "better for the desktop" because of ACPI stuff, should take that laptop and slap themselves over head with it.
 
The work I do doesn’t run on FBSD.

I use FBSD not as a windows emulator but as a lean and solid platform for the uses I need. DNS and NAS are these.
 
kpedersen said:
Indeed. Its a bit like saying:

The only reason why I can't drive a Ferrari is because my cup holder I originally bought years ago for my old Ford Escort doesn't fit on the dashboard.
Click to expand...
can you explain in detail? It is like a parable to me. Installing FreeBSD in a laptop (legacy). is easy. I took of the M.2 board from my HP PC and something mess it up.
 
Rock said:
can you explain in detail? It is like a parable to me. Installing FreeBSD in a laptop (legacy). is easy. I took of the M.2 board from my HP PC and something mess it up.
Click to expand...
If the M.2 board doesn't work in your Ferrari, then leave it in your Ford Escort.

Are you asking which M.2 boards are well supported and known to work with FreeBSD?

A quick scan suggests this one. It mentions FreeBSD 12.1 in the supported OS.
(another link).
 
I find that people in this forum are very civil and reasonable.

I also think that one can decide to change what for themselves was a final decision at one point. It's not necessary to remain true to your younger self; it was less wise by definition.
 
For a NAS appliance and server - FreeBSD all the way.

Desktop (laptop) experience (with freebsd 15) - wifi experience was awful compared to linux (sorry) - yes it can be made to work but its really hit and miss - some people have minimal issues getting it up and running, some get faced with firmware conflicts and a frustrating debugging session to get things working (that was my experience). Some wifi highlights for me on my Thinkpad T480s:

* Intel 8265 wifi got handled by the iwm driver and the performance was atrocious, the cause which I discovered later is due to iwm being a bad driver which is stuck at 2005 'G' speeds due to some driver limitation/bugs (same said hardware on linux runs at 300Mbits out of the box with no faffing around).
* iwx driver was extremely buggy on the said system (I replaced the wifi module on the said laptop to an intel AX210 to tried and use the iwx driver), that driver caused system freezes and it even causing data flow issues on other network interfaces (em0) that should not have been impacted whatsoever (and no it wasnt a network address conflict, my wifi and LAN are on completely different isolated networks with different ip addresses and subnets)... That one really had me scratching my head.
* iwlwifi was the only driver that worked reasonably after all the fuss - but the fun continued - I was told here on the forum (lightly scolded) to not use DFS channels (as I asked why no DFS channels are showing up in the wifi scan). I had to switch my AP to use a non-DFS channel to get wifi to work, whereas linux had absolutely no problem connecting to them (better end user experience) - while I get the argument somewhat about not using DFS channels, what about situations if i took this laptop traveling abroad to other places and the local wifi there was using a DFS channel; so its a good user experience to not be able to connect?
* No WPA3 support?

Misc/Other:
* No DRM support in web browser - yes I know there are a whole bunch of hacks you can probably use (maybe to make it call some linux library to handle DRM) but this as an out of the box experience is not nice. It meant I was not able to listen to any of my audiobooks on amazon audible or watch amazon prime...
* On a desktop system with an NVidia GPU, KDE+Wayland is not stable at all (unusable). Wayland on the laptop with intel graphics worked great. On my desktop with NVIdia, as soon as I select Wayland from the SDDM screen and enter my credentials to log in, I get a kernel panic which looks like a crash relating to DRM or the nvidia driver (not 100% sure which one it is as i am not great at interpreting stack traces).

As a server and NAS appliance OS I love FreeBSD. A a daily driver for a desktop experience, its not a fun experience for me.
I do use VSCode as well so I echo some of the other posts already about editors - I dont want to go back to coding in vi/vim - its 2026.

Thats my experience - I revisit FreeBSD on the desktop from time to time to see where things are at, but for me at least, its not at the state where I'd consider ditching linux for it yet. I will keep checking back from time to time. I am hoping some devs see this and acklowledge that the end user experience for some of the above is not great (rather than me getting a whole bunch of "its your fault because of X, Y, Z").

It would be nice if someone ported KDE's network-manager (or write something similar conceptually) to FreeBSD. Having to edit files in /etc by hand (like wpa_supplicant.conf) is not fun. It feels like the mid 2000's.
 
ahhyes said:
I dont want to go back to coding in vi/vim - its 2026.
Click to expand...

I accidentally read this sentence (the rest I mainly didn't read) and I just want to say that the "it's 2026" is unwarranted and completely unnecessary. I'm sure you are aware that many people love coding in vim and find it the best way to code. It's okay that you don't, but they also live in 2026 and know all the other options and still choose vim.
 
.

This is an unbelievably fifth-column thread. Let's compensate it a smidgen.

I ❤️ FreeBSD

I can't live without FreeBSD.

My life is exponentially better since I dared to install FreeBSD.

I can't understand how I was able to use a computer without FreeBSD.

.
 
ahhyes said:
I do use VSCode as well so I echo some of the other posts already about editors - I dont want to go back to coding in vi/vim - its 2026.
Click to expand...
I recall this one back in the day:
"I use Visual Studio, I don't want to go back to coding in vi/vim - its 1998"

And then this one:
"I use Eclipse, I don't want to go back to coding in vi/vim - its 2009"

I'm sure my distant relatives will experience:
"I use MegaEdit, I don't want to go back to coding in vi/vim - its space year 2942"
 
There, again, 'hardware' problems on desktop are laptop stuff.
FreeBSD is suitable only for laptops that it has explicit support for; ACPI, radio, keyb/mouse, etc. Don't expect FreeBSD to work 100% on a laptop that you bought at random.

Step 0 - you need to consult the HCL. Even myself, that uses workstations and not laptops, constructed out of intel/nvidia that always has 1st tier support, I need to check the HCL to see whether some PCI express studio-grade sound card is supported. Right now I have an offer for a good mid range interface, but in 15.0-RELEASE HCL it is clearly written the driver does not support recording or monitoring. Only playback.

Now if I've bought the soundcard without knowing this I'd be pissed on arrival. Would I have any "rights" to come and rant about how FreeBSD isn't good. Only if the support was lost or degraded, then we can rant. If a laptops hibernation and wireless worked on a previous FreeBSD but it doesn't anymore.

Don't take this as criticism but an explanation how hardware and software compatibility yields a Venn. The overlap between laptops and FreeBSD, and studio interfaces and FreeBSD, is a thin zone. Depending on your real life cicrumstances, you can try to hunt for the hardware in the overlap, if you prioritize software (FreeBSD), or the opposite - ditch FreeBSD for this task and use whatever runs your hardware well.
 
Zare said:
There, again, 'hardware' problems on desktop are laptop stuff.
FreeBSD is suitable only for laptops that it has explicit support for; ACPI, radio, keyb/mouse, etc. Don't expect FreeBSD to work 100% on a laptop that you bought at random.

Step 0 - you need to consult the HCL. Even myself, that uses workstations and not laptops, constructed out of intel/nvidia that always has 1st tier support, I need to check the HCL to see whether some PCI express studio-grade sound card is supported. Right now I have an offer for a good mid range interface, but in 15.0-RELEASE HCL it is clearly written the driver does not support recording or monitoring. Only playback.

Now if I've bought the soundcard without knowing this I'd be pissed on arrival. Would I have any "rights" to come and rant about how FreeBSD isn't good. Only if the support was lost or degraded, then we can rant. If a laptops hibernation and wireless worked on a previous FreeBSD but it doesn't anymore.

Don't take this as criticism but an explanation how hardware and software compatibility yields a Venn. The overlap between laptops and FreeBSD, and studio interfaces and FreeBSD, is a thin zone. Depending on your real life circumstances, you can try to hunt for the hardware in the overlap, if you prioritize software (FreeBSD), or the opposite - ditch FreeBSD for this task and use whatever runs your hardware well.
Click to expand...
According to your post I can rant as my laptop suspends and resumes just fine with 14.x but it hangs miserably with 15 (hangs on second resume) and 16 (hangs at first suspend).
 
My pc cannot boot FreeBSD. I tried DVD and HD. So I took out the Windows M.2 memory to make the pc boot from HD or DVD. Nothing works.
 
Rock said:
My pc cannot boot FreeBSD. I tried DVD and HD. So I took out the Windows M.2 memory to make the pc boot from HD or DVD. Nothing works.
Click to expand...
Sometimes it helps to try another flash drive ("USB stick") - I experienced some that are simply incapable to boot; very seldom, but some don't (search me, I don't know why.) Also the image written could be defective.
If you already ensured, that's all OK, you may check your machine again:
Did you remove any drive which might perhaps contains maybe the slightest rest of some Windows partition? Your BIOS settings? Some machine's BIOS simply prevents by default to boot anything but Windows.
 
Rock said:
My pc cannot boot FreeBSD. I tried DVD and HD. So I took out the Windows M.2 memory to make the pc boot from HD or DVD. Nothing works.
Click to expand...
That must be a unique problem, I have used M.2 and U.2 of every imaginable kind with FreeBSD, all successful and never an issue. Did you try asking about this in the appropriate forum here (with full detail)?
 
Academic Question: which Linux distribution offers the most stable and reliable desktop GUI environment?

My entire workload is windows based so I have zero desire to putz around trying to make my workload run in a ‘nix environment.
 
I don't use FreeBSD on my desktop and my laptop as host development platform anymore, because I currently haven't found a solution to run some proprietary applications which I need for electronic engineering like AMD's (former Xilinx) Vitis/Vivado FPGA IDE and others. So I went back to currently Debian 13. I only run FreeBSD in a VM currently.

But I have planned to use FreeBSD natively on other devices like the VisionFive 2 as firewall for my home network.

OT:
Does Sony still use a modified FreeBSD as their PlayStation 5 operating system? Then I already have a FreeBSD based system running. :D
 
You must log in or register to reply here.
Back
Top