Go runtime: 4 years later

Re:Go runtime: 4 years later by dopidopHN on Monday September 26, 2022 @08:17PM (#32990315)

Look at you guys using nice looking languages! Haha, Java got better, but oh god it’s still verbose.

We got rid of the getter setter silliness to be in “constructor land.” ( immutable records from Java 17 )

Function are still not first class citizens, but … they have a working visa now. You can shove lambda anywhere.

It’s still awkward to write functional code

Meh. Recently I’ve been really productive with it and I like the sheer boredom and lack of surprises.

[ Parent | on HN ]

Re:Go runtime: 4 years later by kaba0 on Tuesday September 27, 2022 @02:02AM (#32991966)

Java is several times more expressive and less verbose than Go, objectively.

[ Parent | on HN ]

Re:Go runtime: 4 years later by RhodesianHunter on Monday September 26, 2022 @11:01PM (#32991152)

Most developers on the JVM with any freedom have switched to Kotlin.

[ Parent | on HN ]

Re:Go runtime: 4 years later by pjmlp on Tuesday September 27, 2022 @11:35AM (#32996718)

Better check those numbers, only those forced by Mountain View minions have done so.

[ Parent | on HN ]

Re:Go runtime: 4 years later by RhodesianHunter on Thursday October 06, 2022 @05:12PM (#33114161)

I'm talking about on the server, not Android... but sure. Bury your head in the sand.

[ Parent | on HN ]

Re:Go runtime: 4 years later by dopidopHN on Tuesday September 27, 2022 @06:06PM (#33001744)

I was free I would not develop corporate software. But oh well

[ Parent | on HN ]

Re:Go runtime: 4 years later by fs111 on Tuesday September 27, 2022 @01:57AM (#32991946)

citation needed

[ Parent | on HN ]

Re:Go runtime: 4 years later by RhodesianHunter on Thursday October 06, 2022 @05:12PM (#33114165)

Any and all language trend survey results from the past couple of years.

[ Parent | on HN ]