Not sure why you’re defending, on a self-selected technicality, a VC company making hostile moves against the Nix project, and the NixOS community, but I’ll bite.
EEE is not a strictly defined term. There is no such thing as ISO-EEE. It necessarily is open to interpretation, even in its original sense. And always has been.
This description you’re using here is a pretty narrow selection of the meaning of Extend. Not only that, but the situation around the competitors not having the bandwidth to support the new features? That’s the last E, that’s Extinguish, not Extend.
With EEE, you have to look at the broader picture. At the whole services offered by the company. That includes the extra services, and also the proprietary additions “around” Determinate Nix
Even with the narrow definition that this would be about abusing a position of power, and “push[ing] novel [features] that other [competitors] don’t have the bandwidth to support”, this is what is happening even in the narrow definition of Determinate Nix 3.0[sic]. The experimental features will be pushed onto customers, put into a shape that fits Determinate Systems’ goals, and other Nix implementation either having to stay incompatible with the fork from the company founded by the upstream project’s founder, or having to stick to their choices.
To recap,
Embrace is self-descriptive here.
We already had Extend via the added hosted services around the Nix ecosystem (some planned did not ship), the additional features around enterprise deployments, and finally the “minor” differences in the default config from Determinate Nix, from before this announcement.
This announcement, taken at face value, assuming every word means exactly the platonic definition, without having a “between the lines” to read from, would be at worst more of the Extend phase.
I don’t think there is anyone disagreeing that Determinate Systems have been Extending Nix and the broader Nix ecosystem.
And here’s where this is interpretation on my part. FUD. The Extinguish phase is now officially started. We are seeing the company taking its privileged place to define what Nix 3.0[sic] is. Whether only through its appropriation of the version number, or through its explicit goals of shipping features before they are done, and deciding their form for when they are done.
(I’m not sure how taking the lead on the learning resources should be considered here. It definitely has already been used to push their agenda.)
NOTE: I am not saying that they have succeeded in the latter E.
Hopefully the Nix project and community is strong enough to again take a stand against the bullying from Determinate Systems, and to continue with their plans toward a good Nix next.0.
Even though I did leave the community (even if it’s not obvious from my apparent lack of ability to let go) I do not want the Nix, Nixpkgs and NixOS projects to fail. It would be a loss to everyone. Whether or not other alternatives exist.
(And obviously, this is all my interpretation of the situation, coming from years of interaction with the different parties involved. Some private, some personally experienced, and some from their continued public actions. I am not speaking in any official manner for anything or anyone else than myself personally.)