It's interesting when you have these old, large, sprawling bureaucratic organizations and the employees hardly give a sh!t anymore and allow for these large vulnerabilities. It's not a money issue, it's a caring issue I think.
If it was CPU bound and multi-threaded then wouldn’t Rust be a lot better? Since it has no runtime or garbage collection, in addition to having good built-in thread safety. Hence my original point.
But those are instances where you can use TypeScript/node.js which is less verbose than Java and has better native async support. Also easier to write tests for.
Also VSCode with Rust Analyzer works decently as an IDE.
You can do everything better in either TypeScript (for cognitively simple things) or Rust (for complex things that need to work correctly and be fast).
The difference is you need to explicitly handle cases that would cause runtime errors where you have to use .unwrap() or match selectors, which makes it safer in general. Since the values are wrapped in Result or Option enums. Code that doesn’t create these types isn’t possible to have runtime errors which reduces cognitive burden when coding.
And yes you can write non-idiomatic Rust that lets you leak memory but it doesn’t happen by accident like in C/C++.
I think Rust is what you need. It basically won’t compile if your code would have runtime errors or memory leaks, except for cases you need to explicitly handle. The linters in VSCode also make it pretty practical to use. It’s been a joy to program in since I started about a month ago.
I’d much rather use a safe language such as Rust that has the same speed without all the worries.
Probably a harder learning curve than Odin or Go but more likely to work and also run faster (than Go at least). It also has zero cost functional programming paradigms.