I advise training programmers instead of throwing them in front of a screen without any training. Companies these days provides no training at all. When I was hired over 40 years ago, I spent plenty of time being trained for my first 3 months. Now, nothing, and you if you want to train a new person, you do it on your own time.
Why train when they just leave the company in a year for 10%+ more money.
The Case for Memory Safe Roadmaps
121–130 of 427 posts
Re: The Case for Memory Safe Roadmaps
#122Their "Appendix: Memory Safe Languages" lists: C#, Go, Java, Python, Rust & Swift
Really, the only memory unsafe languages still in use are C and C++. If it weren't for the behemoth of legacy code we'd really have this problem more-or-less licked. Unfortunately, that behemoth is still rampaging across the landscape. "Rewrite it in Rust" gets a bit of pushback, perhaps even justified, but at this point in time I'll take anything that just reduces that behemoth in size. The journey of a thousand mil…
Re: The Case for Memory Safe Roadmaps
#123But how are we going to trade stocks in nano seconds without C++?!
Actually, I have no idea if FPGAs in HFT are still a thing.
Re: The Case for Memory Safe Roadmaps
#124Confused about Python in particular considering a lot of powerful and common dependencies in the ecosystem starting out from numpy and friends all have C/++ components to them for performance improvements. Surely this is a vector to be considered?
Re: The Case for Memory Safe Roadmaps
#125Earlier quoted context omitted.
If you have no users then go for it. However if you do then you are doing those users a disservice by exposing them to unnecessary risk. Maybe the risk is mitigated in other ways. Your software runs as a cli and not a service. It doesn't process outside input. It is run in an ironclad sandbox. But honestly, if you think the way C++ with RAII want's you to then you should already be following the rules that Rust want'…
so what you’re saying is proper C++ is fine?
Re: The Case for Memory Safe Roadmaps
#126I advise training programmers instead of throwing them in front of a screen without any training. Companies these days provides no training at all. When I was hired over 40 years ago, I spent plenty of time being trained for my first 3 months. Now, nothing, and you if you want to train a new person, you do it on your own time.
Re: The Case for Memory Safe Roadmaps
#127Their "Appendix: Memory Safe Languages" lists: C#, Go, Java, Python, Rust & Swift
Will we one day be able to use AI to make code memory safe?
Re: The Case for Memory Safe Roadmaps
#128Re: The Case for Memory Safe Roadmaps
#129Their "Appendix: Memory Safe Languages" lists: C#, Go, Java, Python, Rust & Swift
Ada people scratching their heads....
https://nap.nationalacademies.org/read/5463/chapter/3
tldr; seems to be that the software development world has changed from the days that DoD was the "dominant" software developer, and Ada in the interim did not get adopted by the commercial sector (with safety critical exceptions in aerospace, etc. noted).
Re: The Case for Memory Safe Roadmaps
#130Earlier quoted context omitted.
[flagged]
Next thing they'll be giving requirements for people building bridges, houses, and gas and electricity fittings. Seriously, I think the time has long since passed software needs regulating. It's a major part of modern society, and as far as I'm aware, most people aren't opposed to building standards in principle.
If we want a safer internet, make them carry insurance against data breaches and fine them a fixed amount, say $1500, for each identity they leak, paid immediately upon proof of pwnage.