The types in Java/C# etc. are what I'd term as object-oriented type systems. They conflate the notion of class and type; while in Typed Functional languages, they just type data, and also gives you Sum Types and Exhaustive Pattern Matching. This is a very different way of programming from object-oriented type systems. Some more explanation here if you're curious: https://protoship.io/blog/an-invitation-to-reasonml/#the-big...
I get that people coming from Ruby/JS/Python world will go "woo, types!" but you don't need to go functional to get that; I wish more of these articles would explain why the nuances of functional type systems, and other benefits of the functional approach, lead to concrete advantages when it comes to building real systems that do useful work.