but i fear that as it has gotten more attention in the corporate world more and more complexity has crept in as said corporate world wants something akin to AD and group policy so that the compute resources can be matched more closely to the division flow charts.
This, in combo with a ongoing "users are sheep that need a shepherd" attitude from certain elements of the community leads to complexity piling on.
[1] https://www.freebsd.org/ports/index.html [2] http://www.freshports.org/categories.php
But that said, letting the compilation of JDK 1.8 run overnight isn't exactly convenient, and for the next install I'm likely to use precompiled packages, confident that I do know how to compile ports on my own should I want to.
FreeBSD provides a quartely branch (enabled by default since 10.2) with prebuilt packages that are supported up to 3 months, to avoid moving too fast and breaking things. There's also the latest branch, with the latest and greatest stuff.
https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/p...
All the ports are simply automatically configured with "--prefix=/usr/local".
In fact, many of the packages are exactly the same from the same upstream. The differences are freebsd specific patches to fix small (like enabling or disabling different compile flags) or large (for example in the case of gnome or openjdk which requires effort to port) issues, but the packages are all there.
I mistakenly assumed that OP was referring to 3rd party applications that were exclusive to FreeBSD.
[1] I reported one of them in the FreeBSD bug tracker (+ patch). OpenBSD was actually really quick to solve this (I think tedu@ patched it), while the bug lingered for a long time with no activity on FreeBSD's end.
Neither approach is necessarily right or wrong, just different.