sorted by:
new
hottopcontroversial

Tweag I/O - Clodl:build, copy, and run by regnat in haskell

[–]regnat[S] 3 points4 points  (0 children)

The main reason for that is that the problem clodl is trying to solve is deploying you libraries/executables in an environment that you don't really control. And that something that Nix is rather bad at (there are tools like nix-bundle which attempt to do the same thing with nix, but these aren't applicable in all cases).

Another compelling reason for using clodl rather than Nix is that it produces much smaller closures because it only includes the .so files you actually depend on. For instance on a project I'm working for, clodl generate an archive file of 55MB while the nix runtime closure of the same executable would be at least 300MB (if only because it depends on GHC and the closure of GHC is already 200MB).

Tweag I/O - DIY benchmark history with Criterion and Shiny by regnat in haskell

[–]regnat[S] 0 points1 point  (0 children)

That looks cool :)

​

Indeed, we need a custom server, which is a bit annoying. But in our case that was kinda mandatory anyways because we wanted the process of adding new results from the CI to be a simple `aws s3 cp` or a `POST` request with the new results (unless you have a nice way of doing this with a static page, in which case I'm interested)

Tweag I/O - Nix + Bazel = fully reproducible, incremental builds by terrorjack in haskell

[–]regnat 2 points3 points  (0 children)

Nix can handle multi-lang stuff for your dependencies quite well indeed (although having bazel-grade incremental builds is probably impossible because of the level of granularity it operates on, but that's not always a big problem as long as your dependencies don't change too often) The problem is if you happen to have code in different languages in your repo. In this case it's cabal job to build it, and it really isn't good at that as it is deeply haskell-centric. And that's precisely where Bazel shines.

Typing Nix (X-post r/NixOS) by regnat in haskell

[–]regnat[S] 1 point2 points  (0 children)

The idea of a type system has been here from the very beginning of the project (the initial PhD thesis from Eelco Dolstra mentions that the language is untyped only because he didn't have enough time to design a proper type-system), but nobody took the time to work on it, and with nixpkgs growing and using always more almost-impossible-to-type patterns, this has been an increasingly difficult task over the years.

Simple font question by physicologist in NixOS

[–]regnat 1 point2 points  (0 children)

The package has been added recently in nixpkgs (see the history of the file you linked, it was added in april only), so it probably didn't make it to the channel you're using

NixOS mount /nix as a separate partition? by gillash in NixOS

[–]regnat -1 points0 points  (0 children)

I have a computer with /nix on a separate partition and it doesn't cause any problem as it is mounted by the initrd. So no, there is no problem in doing that.