alt Hacker NewsGo's garbage collection isn't well suited for an immutable language like Gleam, so the performance would likely be disappointing compared to other targets.
Replies
packetlost • today at 3:03 PM
An JavaScripts is? Rust is probably a more performant target regardless
➕ show 2 replies
The concurrency model in Go is also poorly suited to the BEAM's process model. Goroutines share a heap so you can't do a lot of things safely that processes can do. Having independent memory space for a process allows you to free it safely when work is done without GCing everything and you can also safely share data because you have a copy not a ref.