8 ms·
This is why I believe NixOS is so important. It allows one to completely freeze the entire development environment on one hand, but also does so in a declarativ
by Ericson2314 11y ago
This is why I believe NixOS is so important. It allows one to completely freeze the entire development environment on one hand, but also does so in a declarative, well abstracted manner (vs VM image let's say) so tweaking/porting is actually feasible.
Until well get to a point where building/installing/administrating is not hours of bullshit, research (and free software) will suffer.
- kaeluka 11y agoThe problem here is (EDIT: IMHO) a social one. The question is not "Why does nobody USE NixOS?", it's "Why does nobody WANT NixOS?" And the answer to that is that the incentives are set up such that reproducibility is a waste of time. As a CS researcher, I want to be idealistic. But the field is competitive and I'm not sure how much idealism I can afford. There's considerable effort to bring artifact evaluation into the academic mainstream (I'm actually helping out at OOPSLA this year [1]), and I think this is a good way forward. [1] http://2016.splashcon.org/track/splash-2016-artifacts http://2016.splashcon.org/track/splash-2016-artifacts
- Ericson2314 11y agoI'm not trying to argue the wrong-headed institutional incentives are irrelevant. It is true that once one gets over the learning curve, Nix* gives you artifact reproducability for free, but that still leaves the problem of the learning curve, and caring about reproducability in the first place. Thank you for yours, and others', work making artifact evaluation a priority. Concurrently, people (including myself) are trying to do something about that learning curve. Hopefully both efforts will massively succeed within a decade :).
- kaeluka 11y agoSorry if I've come on too strong. I might've gotten a bit defensive. I've done work in the past that is hard to reproduce and that's not an aspect of my work I'm proud of -- to say the least. Btw, I'm excited about NixOS. It sounds like you're involved. Thank you. I haven't used it, but I'm hoping to find the time soon.
- Ericson2314 11y agoNo you definitely didn't :). I'd say probably a common HN bias is to ignore institutional forces when it is convenient. Glad to hear you are excited about NixOS!
- aub3bhat 11y agoAs an academic researcher I find it absolutely hilarious that you think the complex social problem of incentive structure and competition will be solved by some Unix OS. If you are interested just take a look at the complexity of licensing/ownership of code written by a PhD student at a Research University in United States. If you look at most of my Open Source code, I use AWS AMIs to share both data as well as OS + code, however I can do that only for side projects. The main thesis projects are typically very high value and consequences of sharing it far more complex to understand. https://github.com/akshayubhat/ https://github.com/akshayubhat/
- Ericson2314 11y agoNo that is not what I think at all, see my follow-up comments below. I just think the combination of shitty tools + incentive structure is even more insurmountable. This is a tough problem that should be attacked from as many fronts as possible. > The main thesis projects are typically very high value and consequences of sharing it far more complex to understand. Commercial value, the university is just more stringent on the licensing/ownership restrictions, or something else?
- joshvm 11y agoUsually the university owns the code in some way and you have to check whether there are any IP issues.
- aub3bhat 11y agoThere are several factors. 1. Commercial value. 2. Future grant applications (a competing group not sharing code will have better chance winning the grant.) 3. Future of other students and collaborators in the group. If two PhD students write a paper, the junior student might wish to write extension papers without getting scooped. And many more. Yet if a paper is important enough, independant researchers will often attempt at replication, this nowadays routinely happens in Machine Learning and Vision due to huge amount of interest. Also in several cases replication is fundamentally impossible, e.g. consider a machine learning paper that uses proprietary data from hospital attached to the university, etc.
- eli_gottlieb 11y agoI'm currently in the process of rewriting some of my code for doing certain simulations via probabilistic programming in Haskell. I expected this to be a pain in the ass, but maybe make the code neater. I've actually found the unexpected benefit to be that the code runs deterministically and produces the same results each time, so I know that an apparent result is not going to go away with another run and a fresh PRNG stream.