Patrickmi

If you compare the amount of attention, language bashing, dedication and sweat being put in it I should expect the survey to show at least 75% adoption

There’s nothing stopping language maintainers implementing a feature if you really hate the slow and thoughtful journey then the language isn’t meant for your “ideal programming language”

>Oracle developed a container runtime with Rust to overcome problems with the Go reference implementation.

Did this ever passed experimental stage ?

Where did you get the information that the Go team never wanted Generics, even the hype around having generics yet the stats shows 50% of Go developers wasn’t interested in it

https://go.dev/blog/survey2022-q2-results

The design philosophy is what makes a programming language, any language maintainers could one day decide to have any of these, when you begin to understand “why this is language existed” you begin to understand its purpose

Gccgo at its core may be fast but when it comes to how the go frontend interpret it to gcc ir that pales in comparison than just straight up optimizating the Go compiler

There’ll more opportunities for more optimizations since they move to SSA ir since 1.5 and in turn compile time will definitely go down

You’re overestimating the influence Google as a cooperation has on Go, you think they’re gonna pay for what they’re not gonna use ?

This for sure isn’t meant for performance critical services, best when it comes to appengine

At least we know the problem and the solution to it

Didn’t Elon check the codebase before open sourcing it, like was he expecting everyone to be happy when seeing author_is_elon ?

We can say “general purpose languages” never gets to be popular There must be a reason of wanting to adopt the language not just because “I like it”

I think there was no performance hit on panic it was memory leak being fixed long time ago

Don’t know if use tools like static check but Go’s type system kinda suck without development tools

So Go GC just need a api that pauses GC when it wants to run

But the big difference is time to understand it

When it comes to JS ecosystem, developer common sense doesn’t work because it fast doesn’t mean it’s bound to succeed among its counterparts, the major thing such could help is their ecosystem they are written in

Hmmmm…..

People are naive, am sure he doesn’t know that rust has telemetry

All these situations I blame Google not Go, sometimes people are ignorant when to differentiate Google corporation itself and the Go team

Or I could get the bytes data then create a really big hash table, boom have discovered a glitch in the simulation