4 ms·

As a security guy I love when people have your perspective on memory safety, guarantees my job for a couple more decades. Memory issues are still the source of

• oilbagz 6y ago
  I'm a SIL-4 programmer. If you can find security issues in my code, its because it hasn't .. yet .. been through the rigors of my teams safety certification and validation processes. Check back in a year, and don't forget to start with the code coverage counts. While I certainly concur with your perspective, the context is, C/C++ vs. Javascript. You have so many low hanging fruit in the npm eco-system, you'd be a fool wasting time on my code. Which, incidentally, is protecting millions of peoples lives in 40 countries, while they commute to work every single day... its not exactly the kind of stuff that teenagers unpack for use in searching strings for things .. Finance code should be much, much better tested than the Javascript eco-system allows. There is no reason not to write finance/cryptocurrency code with the same vigor as transportation safety modules. You're totally right that, if my C/C++ codebase were treated the same way as the average Javascript module, you'd be having a field day. But, done properly, you'd have your job cut out for you. And thats exactly what I'm asking for, from those building 'next generation finance software': get it to SIL-4.