Originally posted by mSparks
View Post
And then he finishes with the lame "number of dependencies" argument. Normally, more dependencies are better, it means they're fine grained and you're pulling just what you need. But guess what? For a language like Go that compiles to executable code and links everything statically by default, it doesn't matter if you have a few big dependencies or a lot of smaller one: you're still including just what you use.
[QUOTE=mSparks;n1451566]
and
"Or rather, it's a half-truth that conveniently covers up the fact that, when you make something simple, you move complexity elsewhere."
Both of which are where java shines (you shift the complexity to a self contained jar), and are pretty much essential to getting software to the point it actually pays the bills (aka production ready).
Meh, simple solutions to complex problems are really just facades, water is wet... What else is new?
Comment