3 ms·
The problem with Nix still remains it's documention, as this blog illustrates so well. - MAny links points to a bunch of 404's. - The links that don't 404 go
by whydoineedthis 5y ago
The problem with Nix still remains it's documention, as this blog illustrates so well.
- MAny links points to a bunch of 404's.
- The links that don't 404 go to ubiquitous readme's that have so much information it's hardly a good place to start.
- The demo he provided is the easiest of use cases with a single package and static files. How do I actually build a binary? How to accomplish the pip installs he shows with the Docker file? Why not show a really 1:1 example if it's so easy?
And even if I work through all that for this blog, fat chance I'm going to convince my whole team to do so.
- lilyball 5y agoThe 404s are to the author’s own GitHub repo and are not a reflection on Nix. It looks like they deleted and recreated the repo with the name wagdav.github.com and just didn’t update the links in this post accordingly.
- Proven 5y agoMaybe such folks tend to like Nix.
- whydoineedthis 5y agoBut it is reflective. I've found that sort of thing rampant in it's community, and sometimes it's own docs. It doesn't mean it's bad tech, but will be hard to convince a corporate group to want to use it.