News for hackers. Stuff that matters.
Re:Rust via its Core Values by nickpsecurity on Monday April 04, 2016 @01:06AM (#11419555)
"I want high reliability code that I would literally trust my life to, that can be verified both by the compiler and by any other arbitrary external tool that may assert proofs of things that may be desirable, such as "it never crashes as long as the hardware operates correctly" and "there is never a null pointer exception".

I had a cool idea last night, and I want a website up that implements it by next week."

We're closer to that than you think. The pieces of it are just scattered in quite a few CompSci subfields. Some are done, some getting closer, and a ton of integration work will be necessary to pull it all together. There will still be a gap between the two. Yet, it's nowhere near as big as people think with the right tooling available.

Example of the first such tool from the same woman that founded robust, software engineering:

http://htius.com/Product/Product.htm

A NASA evaluation indicated difficulty with notation, performance hit, and something else. Thing is, modern work in each area that report griped about got to point where gripes should be eliminated. There's also more automation available in some areas with better results. The good DSL's and tools like Cyc showed the body of knowledge necessary for semi-automating the dev process can be developed. Hell, so did StackOverflow's cut-and-paste-driven development. So, the dream is a dream but a similar reality isn't far off if the labor is put in. :)

Re:Rust via its Core Values by jerf on Monday April 04, 2016 @09:59AM (#11421889)
Like I said, I don't think we're at the optimal point yet.

However, when it really comes down to it, writing reliable software and bashing some libraries and bits and pieces together require fundamentally different mentalities. To see that clearly, note how you can learn in just a few weeks to bash libraries together to do some nifty things, but to learn how to write high-quality provable code is always going to be a multi-year enterprise, even for very, very smart people. And you're never going to be able to get rid of that "bashing together" use case... you can offer Bob the manager a spreadsheet that will only produce provably correct spreadsheets for some suitable definition of "provably correct", but Bob ain't gonna use it. It's way more work than he's interested in doing.

A programming language can't force the user to care. If the programming language requires a level of caring in excess of what the user wants, they will use another programming language.

Re:Rust via its Core Values by nickpsecurity on Monday April 04, 2016 @12:35PM (#11423205)
That's true. The mentality is more important. There will consistently be people who barely care.