roberthensing

3 ms·

1.
Imageless Docker Compose for Nix Users(github.com)
2 points by roberthensing 8y ago|0 comments
2.
by roberthensing 8y ago
Hello, Domen Kožar and I (Robert Hensing) are working on a brand new Continuous Integration service for Nix users. Some distinguishing features: * First class integration with Nix * Host build agents where you want * Free plan for open sour
3.
Hercules: CI for Nix users in development(hercules-ci.com)
5 points by roberthensing 8y ago|1 comments
4.
by roberthensing 8y ago
What I like about Nix is that this kind of functionality can be integrated into the Nixpkgs package set, as a function over packages. It's just as easy as writing a machine image or an virtual machine network test, because Nixpkgs has
5.
by roberthensing 8y ago
This approach is already optimal for up to around 40 or 120 packages, depending on whether you want to support old Docker versions. "Where before you wouldn’t bother trying to have your application and database images share layers, wit
6.
by roberthensing 9y ago
Nix does run on Windows Subsystem for Linux these days.
7.
by roberthensing 9y ago
Doesn't solve your support problem, but... Re "revert to a last known good working system state": some distributions provides this capability. For example, in NixOS, your system is similar to a git repository in the sense tha
8.
by roberthensing 10y ago
Or tell the truth about the truth ;) https://www.google.nl/search?num=0&q=the%20truth
9.
by roberthensing 10y ago
Feedback: Firefox support could be better: color picker does not respond, time entry widget is annoying. It would be nice to have a feedback/contact button or info about liquidtime app, an e-mail address, anything. Out of curiosity, ho
10.
by roberthensing 10y ago
There are great tools for that in both Scala and Haskell. In Scala you can use var, which is easy. In Haskell you can write your algorithm using ST and then use it as a pure function by means of runST. The type system guarantees that all su
11.
by roberthensing 10y ago
In Scala, the implicit arguments are implicit, yes, but the parameter is not. You will have to declare the implicit parameter, even if you omit a type signature. I think I forgot to mention the lack of type class coherence. That's also
12.
by roberthensing 10y ago
Well they put in an effort of 1400 man years for just the software. They even built an interpreter, because (flight/trajectory) requirements were changing all the time. Also: "The highest level of testing was performed with a high
13.
by roberthensing 10y ago
Type class instance parameters must be explicit in Scala, whereas Haskell can usually infer them. That might make a free monad approach more interesting in Scala. However, if you really want to introduce this complexity in Scala, you will p