4 ms·
To be fair, it's rare to use anything but int and float64 in most programs, and it's exceedingly rare to use anything more than a couple of different precision
by enneff 12y ago
To be fair, it's rare to use anything but int and float64 in most programs, and it's exceedingly rare to use anything more than a couple of different precision integer types (unless you're writing a binary codec or something).
I don't think you mean "simplicity" here. What's simpler than forcing the programmer to say what they mean? Perhaps you mean "convenience".
- k__ 12y agoBut it's those problems that keep me away from static typed languages. When I had to use Java for a project, most of the time I was casting objects around, because libA didn't use stuff libB needed etc.
- lmm 12y agoJava is far from state of the art (which is fine, it has different priorities). In Haskell/Scala/F#/OCaml the language can do a lot more of the typing for you, without sacrificing any of the safety advantages.
- enneff 12y agoThe Java ecosystem is pretty painful like that. Go's ecosystem is a lot more consistent, in my experience. Honestly, the difficulty expressed by the GP here is way oversold. I spent a decade using dynamically typed languages and I slid into Go with little difficulty. I really appreciate static typing now.