@leftpaddotpy Seeing the board utterly cluelessly trotting down the path of increasingly publicly endorsing that company while evoking "professionalism" makes it aboundantly clear to other companies that being publicly associated with NixOS carries non-zero risk.
It is not even close to the primary issue, but the depth of the recursive self-own here is just so ludicrous. Such wild demonstration of incompetence only serves to further incentivize reduction of exposure.
@buonhobo@popey Over-simplified, nix & nixos has had very little explicit power structure since inception. That has resulted in lots of implicit power being passed around - such as that held by the benevolent dictator who habitually stops by to throw a wrench in procceses, relitegate, protect problematic community members, etc. - with most of their time spent at their heavily related business venture, stacked with undisclosed conflicts of interest.
@yoavlavi You can load a nixpkgs repository from an arbitrary URL and reference packages from there in addition to your default.
Often when I have a PR in a functional state I’ll immediately reference the PR url directly in my conf and use packages from there. Then once the changes make their way to whatever channel I’m on I can retire that reference and use the one from the main channel.
@MouseByTheSea@slembcke@Nifflas@mcc I never saw eye to eye with Perforce. I feel like it and I are from two different worlds and installing it feels like inviting in an adversary to fight for control of my files ;)
@Nifflas@mcc Using git all over the place for a decade and a half, in all sorts of projects & functions, with decent skill at juggling more advanced flows, I still don’t grok how someone can actually _like_ it.
I appreciate systemic aspects just like I might appreciate a database design. Still doesn’t mean I’d be doing data entry by query writing and liking it.
TLDR; Implementation is great, level of abstraction is ridiculous, people presumably have Stockholm syndrome?