I guess in a practical sense, Elm and Rust. I know a little of each of them already, but not well enough to reliably use. I think all the work done to make JavaScript better is basically just trying to make it like Elm, and I think Elm does Elm better than JavaScript does Elm. For Rust, it's in the neighbourhood of C speeds, but C has some serious flaws (IMO) around its memory management, so I think that something like Rust's type system is very important. Plus, that type system is powerful and once I understood the type system better, I wouldn't be surprised if I could approach being as productive in it as in Ruby. Thus, anything that isn't in a browser (and isn't a web service) feels like Rust is the way to go, and anything in a browser feels like Elm is the way to go. I suppose the third question is "what about services?" to which everyone who does services, when they talk about what they want, it sounds like Erlang to me, so I assume Erlang / Elixir are the way to go there. But I don't see myself putting myself in a situation to need that unless hired to do so, so that's lower on the totem pole.
For fun: Crystal seems totally awesome (though it'd be nice if it would start faster), mruby should be a small and useful jump, there's apparently some streaming language that Matz is looking at, I'd be willing to play with it. SpaceX is using some visual programming language, that sounds like a fun paradigm. Python would let me play with Tensor Flow. Idk, maybe Idris or Prolog just to get an extreme exposure to their respective paradigms. OCaml could be fun for a certain subset of playing around (namely parsing). Common Lisp, Chicken Scheme, and Racket all have interesting aspects that make them seem like potential choices within the Lisp world, and I find that world to be fun.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I guess in a practical sense, Elm and Rust. I know a little of each of them already, but not well enough to reliably use. I think all the work done to make JavaScript better is basically just trying to make it like Elm, and I think Elm does Elm better than JavaScript does Elm. For Rust, it's in the neighbourhood of C speeds, but C has some serious flaws (IMO) around its memory management, so I think that something like Rust's type system is very important. Plus, that type system is powerful and once I understood the type system better, I wouldn't be surprised if I could approach being as productive in it as in Ruby. Thus, anything that isn't in a browser (and isn't a web service) feels like Rust is the way to go, and anything in a browser feels like Elm is the way to go. I suppose the third question is "what about services?" to which everyone who does services, when they talk about what they want, it sounds like Erlang to me, so I assume Erlang / Elixir are the way to go there. But I don't see myself putting myself in a situation to need that unless hired to do so, so that's lower on the totem pole.
For fun: Crystal seems totally awesome (though it'd be nice if it would start faster), mruby should be a small and useful jump, there's apparently some streaming language that Matz is looking at, I'd be willing to play with it. SpaceX is using some visual programming language, that sounds like a fun paradigm. Python would let me play with Tensor Flow. Idk, maybe Idris or Prolog just to get an extreme exposure to their respective paradigms. OCaml could be fun for a certain subset of playing around (namely parsing). Common Lisp, Chicken Scheme, and Racket all have interesting aspects that make them seem like potential choices within the Lisp world, and I find that world to be fun.