One thing I hate about LLVM is that once you get into the ecosystem to get “another alternative” or “abandon LLVM” it’s like hell, you get all these nice cool features then implementing a custom compiler for debugging can be much much harder than that
As a Gopher sometimes am always wondering what’s the big deal ?, like proposal rejecting is like a second nature, who want to talk about features about a particular language? esp a language like go ?, maybe because there’s too much “entitled” devs in the rust community ( tbh I wouldn’t be surprised ) well am always here with my popcorn for more drama
It’s simple when you have WhatsApp vs BlackBerry Messenger and we know that WhatsApp wins, you begin to question yourself what’s making blackberry win even tho it’s inferior, then hearing their secret weapon “Simplicity” trying to mimic the secret weapon but yet still wondering why isn’t going as expected, this is what is happening No matter how go improves people will still talk about its past failures with present failures, so you don’t have to worry people will still use the language and its competition
That’s a misconception that cgo is slow, it’s improving and it’s not slow, when it comes to stacks, Go with its resizable stack and it’s concurrency it’s not hard to say that it’s very much Go is different from other languages. From a normal C function call that returns immediately there’s not much over head BUT when C function takes time with the runtime expecting return value, the runtime will try to align with the C stack creating a more traditional stack, I think there’s a proposal for a directive to let the compiler know there’s no need for the runtime to wait
Great to seeing another alternative, But working outside Bun I don’t see “The reason”, speed is great but excessive speed is most times unnecessary. Understand on the level of Bun it’s better to have its own bundler than to use a 3rd party hope it works well with bun
I think you’re overestimating the level of endurance ( google’s money) have on open source. Firstly Google as an Organization needs revenue to support go’s team expenses ( and I wouldn’t be surprised to them if they cut some cash because of OpenAI and MSC threat), open source teams especially in big corporations IMO have limits to resources dedicated especially if the project can’t be placed at the “platform level”, example take android source projects ideally I see no difference how both teams project their will in the direction on where the project will go but google must have a greater influence on android projects because they’re dependent on it seriously (basically 75% of revenue comes there), so what does google that depends on Go?, am pretty sure Go’s codebase hasn’t reached 7% or 10% at most, discontinue Go ?, fine they dedicate few team specific for their use case or just Rewrite it
> Contrast that to Go, which is used in real situations internally at Google. They don't need to spy on their users, they have first hand experience using the tool.
And that’s a big disadvantage if I were to scale the usage of Go then I would say startups and middle orgs occupies like 80% if the Go team work according to logic at google scale, Go wouldn’t be this successful
Every Problem have a Solution, telemetry is good but abuse of anything is bad, if this follows strictly inline to what they have planned just like what they have been doing, I see no problem. Not everyone must be satisfied
This is obviously a trade off, it’s not a bug there’re certain things one must overcome “with time”, even if Go starts using libc am pretty sure the Go team will have their own libc which makes no difference unless it deals with the problem Cgo have
Sometimes I encounter this like 1/10 but it’s annoying for those who hasn’t seen it and not using tests, it’s really good seeing focus on this just hope how they’ll resolve it with Go version
I don’t know if this is a naive statement or you’re saying it with action because basically every open source project with huge adoption have a single org
Is it only me or ….. when there’s a big news about a certain programming language within 2 days open source projects begin to pop up like they’re the main story
> Go has a whole runtime to boot up before ever getting to that point. Many, many layers of setup code. So it's not surprising at all that it has a significantly slower "cold boot"
That’s one misconception you have about Go, when it comes to Cold start uptimes Go is one of the top garbage collected language to compete the likes of C, the go runtime is a progressive runtime it runs together with your code so it’s basically a Vlang code with added C codes