News for hackers. Stuff that matters.
Re:Scala Native v0.1 by taeric on Tuesday March 14, 2017 @07:47PM (#13872611)
Which is ultimately irrelevant here. Consider, C is rock solid safe compared to machine/assembly.

(Though, I tend to share the annoyance of javascript...)

Re:Scala Native v0.1 by pjmlp on Wednesday March 15, 2017 @03:14AM (#13874364)
C is just as unsafe as Assembly, as the weekly CVE entries prove.

The only differences between C and a powerful macro assembler like MASM, is that C is portable across CPU architectures and exposes less internals.

Rock solid?

With all the UB that Assembly actually doesn't have, and the types of memory corruption issues shared with Assembly programming, not really.

Re:Scala Native v0.1 by taeric on Wednesday March 15, 2017 @09:04AM (#13875771)
My point is that safety or otherwise of the target language is just not relevant. Even C has compile errors if you use the wrong type for an operation. Assembly largely does not.

Taken to the extreme, any language ultimately goes down to machine code. So if it was a relevant fact, it would be relevant for all languages.

Re:Scala Native v0.1 by pjmlp on Wednesday March 15, 2017 @09:27AM (#13875899)
> Even C has compile errors if you use the wrong type for an operation. Assembly largely does not.

There are strong typed assemblers, e.g. IBM i.

Also Assemblers don't remove code under your feet, like optimizing C compilers with their UB tricks happen to do, introducing security bugs.