Understand Kumba I'm not against individual developers of GNU/Linux, but all my research points to real innovation coming from BSD, and only questionable enhancement from the GNU/Linux side that takes several attempts to get a half-working solution. Examples:
Device handling: Devfs did need replacement, but HAL made the situation worse with its constant polling and dirty hacks. Udev fixed the problem mostly, but now that's tangled into Systemd. Before you say eudev, I used Arch prior to moving to BSD, and by far it was the best GNU/Linux experience to date. I used eudev, sysvinit and netcfg for device, init and network over systemd for all three. However this broke half of the packages for Arch, made the Arch build system break, and D-bus constantly misbehaved. Point is, I'd love to use a solution that WORKS and doesn't involve me going into Gentoo level of difficulty ( BSD is far easier than Gentoo to setup, even with 'shortcuts' ) On BSD, they now have devd, which can use HAL, but isn't made to, and choosing to not use something like HAL won't break half your packages/ports.
Init system: Sysvinit, if configured BSD-style, didn't have any serious problems other than the method of action, Runit and OpenRC works, but Systemd doesn't! Why the hell does my server need D-BUS if its just a frigging webserver??? Literally on OpenBSD I can fire up NGINX within minutes as it is in base, add my files after some config, good to go!
D-bus: I'm gonna get flak here, I know, but I don't see the point. Sockets by themselves work fine for IPC, and while adding a common way for processes to communicate is cool, why not just implement message passing as DragonFly BSD is doing? AmigaOS proves the message passing model works.
In any case, I have no problem using MIT/BSD licenced kit from the GNU project or any of the GNU/Linux distros, as all of it I have come along is innovative, good material. The same can't be said for GPL stuff, its more like, there's nothing better to use, if you have to use it. Nobody uses it because they want to. Nobody on the OpenBSD project builds code for VAX, Alpha or another dead architecture on GCC because it's good, it's because there's no real option!
In regards to how GCC mangles code under -O3, all I know is, when I'm running code through -O3 to ensure I've not overlooked any bugs at that level of optimisation, the same program run under clang doesn't fall apart when run at that high level of optimisation, but GCC does, quite frequently. I don't care to learn enough x86 asm on my server to understand the code, all I care is: Does it break?
Let me say this though: the GPL's viral nature as a licence that anything it touches must be GPL too is the single most aggravating thing about it. I have less of a problem, significantly less, with the LGPL and CDDL. What pisses me off further is that some people take pride in that and say it's in the name of freedom. By that statement, they're no better than the police officers who abuse people in there custody and say it's in the name of freedom. If the GPL backed off that then I'd just licence my contributions under the ISC licence and build a patch against the original program.
Entire collection up for sale