[tomohawk]

You can, but you can't deploy them. If you really want to keep your services separate, you need a separate JVM installation and jars for each service. Go gives you this automatically with a simple binary. Go's standard library is an order of magnitude (at least) better than Java's, much more comprehensive, much more cohesive, and much more capable.

[carterehsmith]

>> Go's standard library is an order of magnitude (at least) better than Java's, much more comprehensive, much more cohesive, and much more capable

Can you please provide some examples? This would be a useful comparison, as Java had way more time to work on the libraries.

[thelastbender12]

Don't you think it'd be the other way around - the older a language gets, the standard libraries degrade since you can't introduce newer patterns without breaking compatibility.

[carterehsmith]

>> you can't introduce newer patterns without breaking compatibility.

Yeah it is tricky, but Java has a good track record here:

In 1.2 they added all-new Collections API. The old API is still there and still works, though it is not used much these days.

Then in 5 or thereabouts Collections API got generics.

Then in 8 or so, Collections API got streams, magical multithreading etc etc.

Lambdas were added to the language and standard libraries, and so on.

[winrid]

Can't deloy them how? You would still use gradle or maven and package/deploy the same way.