3 ms·
While not strictly the language itself, I find the Java standard library API to be unnecessarily verbose, with often obtuse defaults. Go’s library is sometimes
by doctor_eval 5y ago
While not strictly the language itself, I find the Java standard library API to be unnecessarily verbose, with often obtuse defaults.
Go’s library is sometimes overly terse, but after having experienced both in production, I much prefer Go’s style.
An example is one of the date parsing functions (I can’t remember details now) which will happily accept an invalid date string (eg 2021-02-35) and silently convert it to a valid date (2021-03-07) despite declaring a parsing Exception.
You see, you only get the exception if you call setLenient(false) or if the date string can’t be coerced. For the life of me, I cannot think of a use case for this behaviour, and it certainly violates the principle of least surprise.
- blibble 5y agothe replacement for SimpleDateFormat/Calendar came with Java 8 (released in 2014)
- doctor_eval 5y agoSure, but it is an example of the kind of crappy APIs that littered Java for a long time.
- hbogert 5y agoCrappy apis is not beholden to java. Have you looked at go's timer API? Try to re-use one without inadvertently causing a data race, or get wrong behaviour.
- vips7L 5y agoOr any of go’s file api’s… https://fasterthanli.me/articles/i-want-off-mr-golangs-wild-ride https://fasterthanli.me/articles/i-want-off-mr-golangs-wild-...
- eknkc 5y agoOn the other hand, Go’s time format and parse logic is the biggest pile of shit I’ve ever seen in an API.
- kaba0 5y agoI think Java has one of the best standard libraries out of any language I used. Sure, it has its warts (but the Date class should really not be used anymore over its more modern replacements, which are again, really sane), but it doesn’t make you reach for third party dependencies at every turn, neither for lack of feature nor lack of performance. Sure, you can use hand-tuned collection libs, but it is very seldom needed.