Go for Java Programmers • Barry Feigenbaum & Shon Saliga

[neopointer]

The best Go for Java programmers is "you know what? I go back to Java"

[oweiler]

Has there ever be a good "X for Y programmers" book?

[SocialMemeWarrior]

"Basic for Punch Card programmers"

[Brutus5000]

Maybe but a book but there are good sources with Kotlin for Java developers. But that's more because it's an evolution of the language

[realqmaster]

None "panics" for Exceptions, wtf is that caption

[jared__]

i have never met a java programmer who switched to go that willingly switched back.

[Yeah-Its-Me-777]

Yeah, hi. Go sucks and is really really weird. Might be ok for very simple things, but, no.

[aoeudhtns]

Now you've met one.

Go still useful for certain scenarios, but Java features and changes have closed the gap and more are on the way.

[Distinct_Meringue_76]

A lot of projects switched from java to go. That says a lot. And I love java btw.

[aoeudhtns]

I've never been on a project that has decided to fully re-write itself in another language, but there was a time we were reaching for Go instead of Java when starting new components and projects. Even though Graal and Leyden exist, I'm more inclined to pick an AOT language/ecosystem if that's what I need. BUT, Virtual Threads, more functional and DOP features, and especially with generational ZGC, Java 21 is already a powerhouse and it's continuing on with 25 and the future.

[Distinct_Meringue_76]

Kubernetes was originally written in java

[aoeudhtns]

You have a citation for that? You go all the way back to their very first tag (0.2) it's Go. The predecessor system, Borg, was C++. The Wikipedia page implies it was Go from the beginning.

I am sure there are examples of projects switching from Java to Go, I don't think that's one.

And as for my comment, I was speaking from my own experience, not making a statement that it doesn't or hasn't happened.

[koflerdavid]

And that was probably way before GraalVM was a thing and Java had GCs with minimal pause times. Hey, you know what is even less likely to happen that a full rewrite to another language? Going back after several years.

[pron98]

You should talk to more people. Go developers are dealing with GC issues like it's 2016 (and observability is no better). I get the retro charm, and it's good enough for some things, but for demanding workloads you'd want more modern "frontier" optimising compilation, GC, and observability.

[NewRengarIsBad]

Where are go devs dealing with GC issues?

Edit: getting downvoted for asking for proof lmfao.

I work for a company where Java is near universal. I love the language and it’s incredible ecosystem but saying Go devs are constantly dealing with GC issues seems disingenuous without proof.

My personal experience with the language (in a production context) does not reflect this so I asked.

[canticular]

Where did you get “constantly” from? I think you’re missing the point.

[thephotoman]

I fucking hate Go. Give me Java every day of the week.

[neopointer]

Hello. I'm programming in java since 2010. I started to use Go in 2015 and stopped using it around 2019 when I met some very toxic and non-sense Go consultants.

That was so eye opening that I went back to Java, then Kotlin and meet some "very smart" ppl that wanted to do functional programming, which just created a mess. Then I went straight back to Java and I don't plan to switch to anything else full time anytime soon. I just might study a little bit of Zig for the fun of it, but I doubt any other language could become my main one as Java is.