It all depends on type of project timeline etc. I find the stupid errors in untyped languages trivial to catch. In debugging the hard errors are what takes long

It all depends on type of project timeline etc. I find the stupid errors in untyped languages trivial to catch. In debugging the hard errors are what takes long time to deal with. Those types of errors are rarely can be caught by compiler. On other hand dynamic languages give you flexibility and speed when developing. In some cases that is worth a lot more then losses you suffer from them. Having said that Rust is just terrible application language. It was built for a purpose use it for that purpose. From typed perspective from what I have used recently Swift is probably my favourite. Here comes the catch, libraries, community support all tramp the hell out of almost any language feature. There is a reason we write metric ton of C++ for everything and basically everything Python has C++ and C under the hood. C++ has stuff to do it all, it has been tested polished, tested some more documented and works. Now even Pytorch has first class C++ API.. It’s about time! Java traumatized me as a young engineer fresh out of school. I can’t bring myself to even look at it these days. I am sure it is much better now. I just can’t do it.