Live data from Hacker News

Go runtime: 4 years later

go.dev

251–260 of 296 posts

Re: Go runtime: 4 years later

#251

Earlier quoted context omitted.

Beyond linking it is also a problem with ABI compatibility of object layouts, etc. It is so much simpler with more dynamic languages.

The C ABI on pretty much any platform defines object layout for structs, which is usually good enough.

The C ABI is nowhere near enough for passing arbitrary Go structs, all you need is a map or a sync.Mutex field and you need to exactly match plugin compilation to caller compilation.

I wish https://pkg.go.dev/plugin was clearly documented as not being a viable 3rd party plugin solution.

Re: Go runtime: 4 years later

#252
post #155
post #142

Earlier quoted context omitted.

What do you have against BLM?

Not him, but people outside of US don't care about US social and political issues. Even if Go is used 90% by Americans, website for programming language is still not a place to push politics.

So, if people inside the US said that about the plight of people in Europe and various particular countries, would you agree? Somehow I don't think so. Let's not let bias, blind us to important socio-economic or human rights issues.

Re: Go runtime: 4 years later

#253
post #201
post #142

Earlier quoted context omitted.

What do you have against BLM?

My personal opinions aside, what does a programming language has to do with a political movement in one of the 195 countries in this world? Nothing, that's what. The political activists hijacked the Go community they had access to and power over for their own personal beliefs and agenda disregarding every bit of ethics or responsibility they were entrusted with. As the saying goes, with great power comes great respon…

Interesting. So when you see talk about aiding those whose lives were destroyed in the present war in Europe or facing disasters like floods, is that your stance as well, that somebody is pushing another of their causes down your throat?

We can pick and choose, but let's not act like bias is not involved.

Re: Go runtime: 4 years later

#254
post #113

Earlier quoted context omitted.

Rust has set the bar so high that it’s going to be hard for other languages to justify their use. If I had to make a bet, I’d say Typescript will take over for everything not performance critical and Rust will fit in every spot that either requires high quality assurance or high performance.

Right, and no one will use Go, Java, Kotlin, Elixir, Ruby, Python, JavaScript, Haskell, OCaML, Ada, Lisp... anymore /s.

No post body was provided.

Re: Go runtime: 4 years later

#255

Earlier quoted context omitted.

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 l…

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

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

Re: Go runtime: 4 years later

#256
post #238

Earlier quoted context omitted.

Quoted post unavailable.

That's complete and uncalled for troll nonsense. V has hundred of releases ( https://github.com/vlang/v/releases ), with hundreds of contributors to its open-source project (577 and growing). It exists and works. It's one thing to like some other language, its another thing to spew disinformation, lies, and flames about others.

It has an automated release generated every week. The could be no commit activity whatsoever and there would still be 52 "releases" of V every year.

It's one thing to like V but it's another to constantly repeat misleading information in an attempt to give it more credence than it has.

Even V's own changelog only contains 28 releases (mostly from the 0.1 era in 2019 - early 2020) not "hundreds" like you've claimed.

https://github.com/vlang/v/blob/master/CHANGELOG.md

Re: Go runtime: 4 years later

#257
post #151
post #146

Earlier quoted context omitted.

I found it much easier than java, and a bit harder than python, for reference

What is hard about Java? It is a very small language.

All the weird folders nested into folders, the verbosity, the difficulty to follow logic, all the crazy patterns. I guess you also have all the OOP stuff that doesn’t exist in golang. I always felt like its impossible to write java without a beefy IDE

Re: Go runtime: 4 years later

#258
post #150
post #144

Earlier quoted context omitted.

I think if Golang would have been invented a couple of years later it def would have had sum types. But then, Rust probably wouldn’t have had its insane tooling that is most likely inspired by golang

It’s not like sum types weren’t known a decade before that. Or generics. They just didn’t care.

what imperative language had them?

Re: Go runtime: 4 years later

#259
post #155
post #142

Earlier quoted context omitted.

What do you have against BLM?

Not him, but people outside of US don't care about US social and political issues. Even if Go is used 90% by Americans, website for programming language is still not a place to push politics.

It sounds like it's more than "don't care", it's a "I'm appalled enough to make a comment"

Re: Go runtime: 4 years later

#260
post #138

Earlier quoted context omitted.

That’s probably because you’re not used to it. I think it’s common knowledge that Golang is easy to read.

Couldn't the same be said of rust though? The biggest barrier, in my experience, is almost always familiarity with the syntax.

I work mostly with Rust, and have been for years, and no I wouldn't say that Rust is easy to read. It's easier to read than most legacy languages, but it's nothing like Golang.
Post reply on HN