While true & I remember folks actually using this in arguments for ‘slow development’, there is some merit to versioning differently for something expected to get minor updates to perpetually follow latest specs such. I can’t imagine trying to discern what a “breaking change” would be in this context. Or would you make a new version for every visual redesign? Dates might have just made more sense, but maybe ESR is easier to follow with the current scheme.
It’s pretty hard to fight hegemony when your salary is just built on donations. A lot of important tech is also paid for via government grants then the private sector gets to use it and erect the walled gardens when it should be in the commons.
Authy requires a phone number last I checked & is a part of a for-profit entity. TOTP management is a simple task so there is no reason not to be using something open source.
It was usually recommended to lock to inputs anyhow with all the fetchers requiring a hash which I hated having to manually update & like the UX flakes provides (I really wish they supported more than Git & Mercurial tho). You can still have different evals tho if you point to latest.tar.zstd or other non-hashed thing like a branch where the referred to can change & it won’t reproduce. I haven’t used channels in years, but doesn’t that just refer to the running system, not using Nix to build projects?
Saving the dependency is pretty big since each flake you import will bring along its jungle of dependencies now in your downstream project. I can’t think of a use case where < 10 lines is worth a dependency—especially since as you noted, lib has the glue right there for you to put it all together.
I dunno, I don’t trust a guides still recommending flake-utils. You can make the same four loop in like 4 lines of Nix which is a smaller diff & doesn’t pollute your downstream consumers with a useless dependency. Flakes also don’t eliminate pointless builds, fileset or filtering the src can & the only tool with file tracking on by default is the Git VCS specifically (which also involves the intent to add flags which is the other side of annoying).
The more the number change in that direction, the more game devs will not choose to ignore non-Microsoft Windows options too moving the needle to native support. Imagine a future where a game only works after enabling WSL with command flag workarounds if you want to play on a proprietary OS 😂
It’s not compatible with other Markdown forks, but the whole Markdown ecosystem is a mess duct taped together by more forks & extensions that aren’t compatible either. Even the common denominator CommonMark is feature-barren & isn’t suitable for documentation or technical writing, but boy howdy will the next guy have his Markdown contraption to sell you.