News for hackers. Stuff that matters.
Re:Lexical differential highlighting instead of syntax highl... by Analemma_ on Thursday July 11, 2019 @04:29PM (#20415490)
> In 2013 I was working in nuclear power plant automation ... the job required reading a lot of assembly code.

Does anyone else find this terrifying? Nuclear power plant automation should be done in the safest of the safe languages. I would be alarmed at the thought of stuff like this being written in C, never mind in assembly!

Re:Lexical differential highlighting instead of syntax highl... by holy_city on Thursday July 11, 2019 @05:01PM (#20415806)
Not really. There are plenty of chips out there without even a C compiler. Some don't even support Turing Completeness. There's even more that were designed and installed before manufacturers started slapping C compilers together for their DSPs, FPGAs, and MCUs.

It would be weird to care about memory safety when your board doesn't even have a heap!

Re:Lexical differential highlighting instead of syntax highl... by ARandomerDude on Thursday July 11, 2019 @04:41PM (#20415620)
To me, it's less terrifying than a complete rewrite in a modern language. Modern languages are great. Rewrites are often littered with bugs.
Re:Lexical differential highlighting instead of syntax highl... by pvg on Thursday July 11, 2019 @05:07PM (#20415854)
Systems like that tend to be designed with different kinds of safeties. A mildly silly example - your typical Rails app doesn't have a watchdog timer, your toaster probably does.
Re:Lexical differential highlighting instead of syntax highl... by okaleniuk on Friday July 12, 2019 @01:21PM (#20422413)
An excellent example!
Re:Lexical differential highlighting instead of syntax highl... by sixplusone on Thursday July 11, 2019 @04:44PM (#20415643)
Yes he said reading assembly, not writing. Whatever they use, I'm glad that someone's having a glance at what the compiler spits out. Also could be talking about microcontrollers, and in an industrial setting PLCs wouldn't be unexpected.