Python and Ruby. I don’t see how you could not want static typing. Not least because of it’s documenting qualities. Otherwise what are we relying on variable an

Python and Ruby. I don’t see how you could not want static typing. Not least because of it’s documenting qualities. Otherwise what are we relying on variable and method names to tell us what type something is?! Ha ha. Lisp OTOH I could forgive the non static typing for the learning opportunity but not sure I’d use lisp for production code for the same reason unless there is a type checker utility. I’ll put up with JS because of the Web and I can use TS but for server side I won’t use Ruby and Python as I can slot in C# or Java or Haskell and have much better time. Finally Elm: definitely worth learning but hit its limitations pretty quick. The problem is you have to route everything in your app through their mandated UI pattern (imagine a web app where every piece of state including the currently viewed month of a date picker 20 levels deep HAS to be a React prop on the root object updatable only in in one root place with no abstractions like interfaces or type classes or even hell monkey patching dynamic language stuff to tame this problem).