3 ms·
It's not really a question of being conservative but of being professional, I would say. Using unstable anything on production software is not professional, on
by ElBarto 8y ago
It's not really a question of being conservative but of being professional, I would say.
Using unstable anything on production software is not professional, on mission critical software it is reckless incompetence.
- wongarsu 8y agoDepending on your testing and release process using an unstable compiler may not be a big deal. Unlike a webserver or a JIT you run the rust compiler once with your final product and can spend as much time as you want to verify the result.
- ElBarto 8y agoBut then the question is: what's the point? Any difference between production and dev/testing environments should be justifiable. Certainly in the last testing stage there should be no difference at all. Nightly builds of any software are only there to enable testing 'in the wild' of that software. There's no justification for any other use. Edit: The Rust community really needs to grow up...
- dang 8y agoWould you please stop posting flamebait to HN? https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- ElBarto 8y agoI thought I had posted constructive comments on this discussion. If discussing good software practices is "flamebait" that deserves to be downvoted, which was what my "growing up" quip was about, then I am at a loss as to what to do...
- jhasse 8y agoI think he means your "growing up" quip.