3 ms·
> Uses commonly accepted approaches, libraries, style I would argue NOT to do this if you're writing Java. Java paradigms are awful, lead to way too many laye
by Sohcahtoa82 4y ago
> Uses commonly accepted approaches, libraries, style
I would argue NOT to do this if you're writing Java. Java paradigms are awful, lead to way too many layers of abstraction, and code that is impossible to debug because your stack traces are just 30 calls of ".invoke()".
> Readable by programmers who'll work with that code in the future.
And yet Perl became popular.
- ben_w 4y agoJava was the language of choice when I was at university. The way they described it to us, was that everything about it was designed with teamwork (and large teams) in mind. I don't know how well it really did that even by the standards of the era of its introduction, but it has the air of plausibility. Certainly, I expect anyone who is used to that style to prefer to encounter and work with Java written in that style over Java written in the style of C. > And yet Perl became popular. As I recall, the joke being that it was a "write only" language.
- Sohcahtoa82 4y ago> As I recall, the joke being that it was a "write only" language. Yeah, which is why I question how it go so popular.
- ben_w 4y ago"Write only" means nobody works with it once it's been written ;)