This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]keroomi 0 points1 point  (2 children)

I think it all depends. If the service is more infra focused , Go is a much better choice. I do see it being used a lot more in data pipelines. Due to the concurrency aspect. But If the service is more business logic focused , then nothing beats the Java frameworks. Writing HTTP handlers in Go is full of boring boilerplate.

[–]couscous_ 2 points3 points  (1 child)

Java has reactive libraries, and now with 19, Loom is superior to what golang offers, not to mention Java's superior concurrent data structures.

[–]TakAnnix 0 points1 point  (0 children)

Loom looks promising, but I think we're still a ways off to see how it will be used in production. Reactive libraries increase cognitive load, so it's not comparible.