I don't think people will migrate to Go, as they most likely chose Node (or Deno) because of full-stack Typescript or Javascript. People who need the great performance of Go are probably already using it. For a Rust, Typescript, C#, Kotlin or the like user, Go is a hard pill to swallow due to it's limited type system and cumbersome DX. Also, Go modules are typically un-intuitive.
I also think that Bun will have a very hard time to become relevant. The hype is already over. Their benchmarks and marketing are old and sketchy. I mean, they're using uwebsocktesJS under the hood, which you could use with Node or Deno as well, if it's important to you to serve 2000000 times per second a static "hello world". Startup times for JS runtimes have been debunked recently. (You can prepopulate some caches which makes the startup surprisingly fast, https://deno.com/blog/aws-lambda-coldstart-benchmarks)
If you take a closer look at Deno's core api and std lib, there's much to like. The advantage compared to Node a significant, but I agree that they might not be decisive for most projects. Time will tell.
Comments
It looks a lot like they ended up back at a solution that looks like package.json with npm.
And now node has typescript. So end of Deno I think. I think people will migrate to Go anyways or Bun (if it works) in the long run.
I don't think people will migrate to Go, as they most likely chose Node (or Deno) because of full-stack Typescript or Javascript. People who need the great performance of Go are probably already using it. For a Rust, Typescript, C#, Kotlin or the like user, Go is a hard pill to swallow due to it's limited type system and cumbersome DX. Also, Go modules are typically un-intuitive.
I also think that Bun will have a very hard time to become relevant. The hype is already over. Their benchmarks and marketing are old and sketchy. I mean, they're using uwebsocktesJS under the hood, which you could use with Node or Deno as well, if it's important to you to serve 2000000 times per second a static "hello world". Startup times for JS runtimes have been debunked recently. (You can prepopulate some caches which makes the startup surprisingly fast, https://deno.com/blog/aws-lambda-coldstart-benchmarks)
If you take a closer look at Deno's core api and std lib, there's much to like. The advantage compared to Node a significant, but I agree that they might not be decisive for most projects. Time will tell.
I hope they rather chose a BEAM, JVM or CLR based language, if not Typescript.
The constant churn of the JavaScript ecosystem has me heading back for ASP.NET