-
-
Save willbprog127/05db7a43d889ca70da21 to your computer and use it in GitHub Desktop.
| * Base system is fine, and my change from AMD processor / ASUS motherboard to | |
| Intel / Gigabyte seems to have made nice performance improvements | |
| * Packages are where the problems lie... | |
| - PCManFM: When doing certain file ops, the list of files does not update, | |
| showing stale info. I think this is due to hacky workaround with glib and gtk2 affecting kqueue | |
| - Eclipse: Crashing and reliability issues compared to Linux counterparts | |
| - gtk-vnc: Package does not have python bindings and doesn't work properly with py27-gtk2 | |
| - VirtualBox: Package is pretty stale, still ver. 4.x.x while latest is 5.x.x | |
| - Audacious: Audacious will start using 100 percent CPU after running for a while. | |
| No problems on Linux with same prefs and music library. | |
| - Python2: Python2 crashes and dumps core one out of ten times while the same python2 | |
| app may crash one in thirty times on Linux. | |
| - ntpd: System time was fine one moment, then five minutes later was off by an hour or more. | |
This may not seem like a really big deal to some folks, but I run a small business supporting multiple customers, and I can't have my pygtk support tools disappearing on me right in the middle of a fast-paced support session.
The other issues are pretty irritating too, especially Audacious pegging CPU usage to 100 percent...that can cause noticeable drag on the system.
System time varying more than 10 seconds or so is pretty bad, but more than an hour?? Wasn't hardware clock because it's just fine on Linux.
After a while, when there are too many things going wrong with an OS, it gets wiped and I try to find something more reliable. I really like FreeBSD's simplicity and security, it just stinks that the package situation is so unfavorable compared to the bigger Linux distros.
😢