As long as it's a low level language and developers are active in maintaining the project, it's fine. It will be fast enough and stop making anything frontend related atrociously slow.
The reason a good part of the community would have preferred a rust port over a go one is stability.
I'm tired of software that crashes or misbehaves; having a good type system and good memory helps reducing the chance of that happening.
The perfect example of this is bun.
- Nice to have TypeScript running by default
- Nice to have a lot of new APIs
but the segfaults are HORRIBLE. I still have to switch back to tsx (most reliable way to run TypeScript files without hassle nowadays, don't touch node-ts) every once and then because I get.
I've never had that with deno and deno got a fraction of the development (and never really established itself, plus the go-like http import were terrible - I woulnd't recommend deno overall, bun still wins)
Software written in Go is not as bad as software written in Zig, but I still got enough problems with go dependencies that I try to avoid them if possible. I dropped software by Ory and Sentry because of this.
Of course it's possible to write nice software in any language: I've never seen Redis segfaults, for example. Docker has been good to.
But not every project can have the amount of resources needed to get there. With software written in Rust the chance I'll get something working are higher.
As long as it's a low level language and developers are active in maintaining the project, it's fine. It will be fast enough and stop making anything frontend related atrociously slow.
The reason a good part of the community would have preferred a rust port over a go one is stability.
I'm tired of software that crashes or misbehaves; having a good type system and good memory helps reducing the chance of that happening.
The perfect example of this is bun.
- Nice to have TypeScript running by default
- Nice to have a lot of new APIs
but the segfaults are HORRIBLE. I still have to switch back to tsx (most reliable way to run TypeScript files without hassle nowadays, don't touch node-ts) every once and then because I get.
I've never had that with deno and deno got a fraction of the development (and never really established itself, plus the go-like http import were terrible - I woulnd't recommend deno overall, bun still wins)
Software written in Go is not as bad as software written in Zig, but I still got enough problems with go dependencies that I try to avoid them if possible. I dropped software by Ory and Sentry because of this.
Of course it's possible to write nice software in any language: I've never seen Redis segfaults, for example. Docker has been good to.
But not every project can have the amount of resources needed to get there. With software written in Rust the chance I'll get something working are higher.