When I copy or do anything on the Raspbian Linux PI, it takes time and likely will hangs for seconds to minutes.
Never seen that problem. Just tried it to both of my Pi that are in "production", and logging in is nearly instantaneous. Normal shell commands (ls, cd, cat, mkdir, copy files around) is as fast as I can type. I don't use them with big files. OK, just for a test, I decided to mess with big files: On one of them, I get a daily data file (it contains measurement of water pressures, tank fill levels, and such), and each file is ~300K on average. Decided to bzip2 all of the ones for 2017 and 2018, about 450 files. Took about 2 minutes, and was completely CPU limited. No IO problem, no unreasonable delays.
You may anytime go to buy one Belkin.
You didn't read my message above. If I wanted to use a USB WiFi dongle, I would probably find one in the box of random USB parts in the basement. But I don't want to, or can't. On one of the production Pis, there is no free USB port (it is a RPi0W, and the only USB port is already in use). On the other one (a RPi3B), 2 of the 4 ports are in use, and I really don't feel like increasing the power consumption by plugging more USB hardware in. That Pi runs on a 12V battery, which is charged when there is normal electricity, but has to feed the RPi and a few other things when there is a power outage, which too often happens at night, when solar cells don't work. So there I try to run as lean and mean as possible, as far as hardware is concerned.
Power, go for this with a RPI3b if possible:
Which is exactly what I use for the Pi when it is on the lab bench, or being used on wall power. But see above: power is much more complicated than finding a power supply.
4.) Install FreeBSD
5.) FreeBSD on PI with Wifi !
I have done that. I ran FreeBSD on the Pi for about two months. There were problems left and right. The lack of WiFi was the killer one, which made all other problems seem irrelevant. The other problems involved audio (which is not really important), some hassle with Dallas 1-wire (I already forgot the details), and the need to do bizarre kernel compile and configuration exercises for using parallel GPIO port pins which on Raspbian are trivial. I just don't have time to tinker with these things.
The real difference is this. To me, the RPi are a tool to get a job done. If something gets in the way, that something either gets worked on and solved, or replaced if solving it is too much work. On the RPi, FreeBSD was getting in the way, so it was replaced with Raspbian. Do I like Linux? No, but I can live with it, and use it productively. I can even configure and manage a new service using systemd (requires a little bit of gritting my teeth, but it gets the job done). Do I like FreeBSD? Yes, but I don't run around claiming nonsense like "FreeBSD is perfect and the solution to everything".
For how long have you been using Linux actually?
Since about 1993 or 94, starting with kernel 0.99.13. On a 386-40 without FPU. I think my first contribution to the Linux kernel even happened before version 1.0 (I happened to be the only person on the planet using an Exabyte tape drive with a SCSI card that used the Apple 25-pin connector on Linux, so I had to do a minor patch to the kernel right away). I remember going to drink beer with Linus in 1994, before he even had a steady girlfriend (but he was heavily into beer, we went to "99 bottles of beer" in Santa Cruz). I remember one time HPA joined us too.
In those days, I used the SLS distribution, then Yggdrasil, then Slackware, and a few random others. Each of them was a stack of floppies several inches tall. I think the first time I ran X may have been on that 386 (although I had to get an FPU, since font rendering is actually floating-point intensive), but I quickly got a 486-33 and a network between the two (initially it was PLIP, with the two parallel ports connected to each other, until I could afford ethernet cards that were supported). With that one could do a kernel compile on one machine, while the other was doing production work (data analysis). The house we lived in was built very strangely, and there were de-facto no electrical outlets in the living room. But the spare bedroom that had the two computers had no heating, and in the winter got ridiculously cold. So I ran a serial wire and extension cord to the living room, and in the winter my wife and me took shifts to do computing on a VT200 emulator in the living room. Fortunately, my work gave me a "really fast" modem (9600 baud!), so we could be quite productive with two phone lines.
I have been running Linux at work continuously since the late 90s (in addition to a slew of other OSes that cost real money).
I don't remember how long I've been using *BSD. I never logged into a real BSD 4.2 or 4.3 machine for serious work, although I used a friend's account on a VAX 11-750 running 4.2 for a few days. I started using Ultrix (which was in reality nothing but a rebranded BSD) on a MIPS-based DECstation in the late 80s. Then I switched to SysV based Unixes for a long time, all through the 90s (with a bizarre interlude of having a NeXT on my desk for a year or two, most annoying computer ever). When I bought my 386-40 for home in the mid 90s, I was attempting to purchase BSD for it (at the time, there was no free option of running BSD on a x86, Bill Jolitz hadn't made 386BSD production-worthy yet). But the BSDi people were unable to deliver a functioning version of X that worked with any graphics card that existed in the real world (like the Tseng ET4000), which is why I ended up installing Linux instead. I only returned to running *BSD at home in the early 2000s, because of OpenBSD.
For about 10 years (from roughly 2005 to 2017 or 18), there were no Linux machines at home, because the laptops had migrated to MacOS, while the servers and firewalls were *BSD. The Raspberry Pi machines were the first time I went back to using a flavor of Linux at home, simply because FreeBSD was not workable.
