Wow, if that matures, ie gets some real world adopt by serious companies it would be the best thing around.
Much like using Rust and Haskell for web I'd much prefer deferring as much to something like Vue and the server APIs (no sever side rendering for that yet so I mostly just IRL use nuxt.js for toy projects). Something Servant (Haskell) does a clean job of. But you can never completely do away with static heavy lifting
This one takes a more modernized Rails or Elixir's Phoenix approach which is really interesting and looks highly usable.
Community size and quality is everything for real life software (something I remember Clojure had early on and now Rust has in spades, best of breed sort of libraries to choose from) so I hope it gets some adoption to see where it goes. I'll give it a shot to toy around with when I get some time.
> Make sure you have good internet and can wait up to 30 minutes to complete the download [of version 16.10.2020]. We highly suggest to make sure your coffee machine is working before starting the update.
If you have good internet connection it's usually downloaded a lot faster. We have switched the nixpkgs version in that version, so a lot of tooling had to be redownloaded. E.g. in our getting started video we install it on a fresh empty macbook: https://www.youtube.com/watch?v=PLl9Sjq6Nzc&feature=youtu.be The full download there takes around 9 minutes on a slow home office internet connection (it's speed up in the video, but you can see the real-world time at the top right).
> Additionally Nix is very hard to install. This is a stumbling block for a lot of people. Especially when using certain macOS systems you cannot even install nix at all. Luckily most of the nix problems, like the macOS issues will be solved with time.
It's a complete end-to-end solution with an opinionated approach and unstructured documentation.
That is, the learning curve is very steep.
That said, for new projects I'm doing packaging and containerization in nix, because I don't have the time or mental energy to deal with half-assed solutions anymore.
I looked at nix a while ago, concluded the versioning/chesumming is - a given sum should represent kind-of the same thing, but can mean really anything.
There was even a post on how to have a stable version for a tracking branch.
Now, I wouldn't mind, if it were explained exactly what guarantees the hashing provided, but there seemed to be pervasive misconception on what it provides.
It's a truly batteries-included way to get started with building real world haskell web apps in minutes.