I never liked Go, but I admit I like it a lot more if it means I don't have to deal with Maven and other dependency systems as much like the slides say. I've been doing Android since it came out, but before that I was J2EE, and it could be hell if Hibernate needed a different version of a dep than something else in your code stack, for example. Handling JARs by hand stopped working, and the countless XMLs files listing deps for all parts of the system and library started getting full of overrides and the like. Eventually Oracle rewrote all the class loading for their app server which allowed dependencies to have dependencies which were invisible to apps using them. So something as basic as class loaders had to be completely reworked to deal with this, and it was still damn complex and a pain in the ass.
>I never liked Go, but I admit I like it a lot more if it means I don't have to deal with Maven and other dependency systems as much like the slides say.
Hrm, yeah, there are alternatives here. (Not in Java-land...other places.)
> I've been doing Android since it came out, but before that I was J2EE, and it could be hell if Hibernate needed a different version of a dep than something else in your code stack, for example.
