3 ms·
Still no type inference, pattern matching, or ADTs. In a statically typed language that causes lots of verbose ceremony that shouldn't be needed in the 21st cen
by bjz_ 11y ago
Still no type inference, pattern matching, or ADTs. In a statically typed language that causes lots of verbose ceremony that shouldn't be needed in the 21st century. We've known how to do this stuff for decades.
That said, I would take Java's verbosity over Ruby's lack of static types. I write Ruby in my day job, and refactoring is a pain, and the same old type errors keep popping up day after day, causing 500s in production. It seems no amount of TDD can prevent them.
- bliti 11y agoAgreed. It does cause lots of verbose ceremony, as you put it (I'm stealing that). Its quite the experience using a Java IDE and noticing how much code is automatically included by pressing tab. Quite comical that Netbeans has shortcuts words for printing to terminal. Your second point really hits home. I've been battling with Python and runtime types. Its just the nature of the beast. That's why I've been focusing more on languages with solid type systems. I will happily trade verbosity for types. :)