If you want to impose on people to learn Haskell and Nix to contribute, you're going to end up in a lonely island. Remember, Nix tries to be approachable to everyone and that's why it's minimal and simple.
A lot of developers do realize that bash is terrible, but it wasn't replaced yet exactly for that reason. Legacy matters. On Fri, Jan 30, 2015 at 5:07 PM, Oliver Charles <[email protected]> wrote: > Not sure if you're serious, but the last time we considered even rewriting > the scripts in C, people were mostly against that. However, I guess with > this the major opposition (can't read the source code easily) goes away, > because you can still cat the scripts. However, I'd imagine that the > startup overhead is now higher than bash, and the size of closures goes up > a lot (you have to pull in the many hundreds of MB that GHC needs). > > So while it's a nice idea, I don't think it's practical to be done system > wide - though I'm all for doing it locally! > > -- ocharles > > On Fri, Jan 30, 2015 at 4:02 PM, Joe Hillenbrand <[email protected]> > wrote: > >> http://www.haskellforall.com/2015/01/use-haskell-for-shell-scripting.html >> >> Time to replace all shell scripts in Nix with Haskell? >> >> _______________________________________________ >> nix-dev mailing list >> [email protected] >> http://lists.science.uu.nl/mailman/listinfo/nix-dev >> >> > > _______________________________________________ > nix-dev mailing list > [email protected] > http://lists.science.uu.nl/mailman/listinfo/nix-dev > >
_______________________________________________ nix-dev mailing list [email protected] http://lists.science.uu.nl/mailman/listinfo/nix-dev
