Re:Criticizing the Rust Language, and Why C/C++ Will Never Die
by lambdaelite on Tuesday May 12, 2015 @11:34AM
(#9532510)
Right, which is why a subset of C or C++ (like MISRA) is used for critical applications.
[ Parent
| on HN ]
Re:Criticizing the Rust Language, and Why C/C++ Will Never Die
by monocasa on Tuesday May 12, 2015 @12:26PM
(#9532862)
My day job is currently writing embedded high availability code to a slightly modified version of the JSF coding standard (which is itself a modified version of MISRA for C++). There's a lot of safety that Rust would give us on top of C++ with the coding standard's rules, and we're waiting for Rust to simply mature a little.
Re:Criticizing the Rust Language, and Why C/C++ Will Never Die
by lambdaelite on Tuesday May 12, 2015 @12:59PM
(#9533120)
To me, it seems like in the future Rust could occupy the same niche as Java + RTSJ does presently. I'm just not clear on how or why Rust would be sufficiently better to overcome the track record of Java + RTSJ.
Re:Criticizing the Rust Language, and Why C/C++ Will Never Die
by monocasa on Tuesday May 12, 2015 @01:20PM
(#9533321)
JITs and interpreters suck for realtime, and there's only so many optimizations that an AOT compiler can do to a Java codebase (hence why JITs ar so prevalent for Java). Pushing all of these verifications into compile time significantly reduces the run time requirements.
Honestly I see Rust as (potentially, down the road) being a better, less verbose Ada than a better C++ or Java. You tend to write Rust code much like you would an Ada or VHDL program.
Re:Criticizing the Rust Language, and Why C/C++ Will Never Die
by lambdaelite on Tuesday May 12, 2015 @01:47PM
(#9533543)
Both JamaicaVM and PERC seem to have favorable requirements when run with AOT compilation, and the JIT compilation didn't seem too onerous either. What problems have you run into?
I ask because I'm in the process of spec'ing out a safety critical medical device, and JamaicaVM is the lead candidate at the moment.