3 ms·
- Typescript doesn't protect you at all against external data. - A Go program runs single-threaded, unless you explicitly tell it not too, so I don't quite see
by tgv 2y ago
- Typescript doesn't protect you at all against external data.
- A Go program runs single-threaded, unless you explicitly tell it not too, so I don't quite see that as a plus for Typescript.
- Go is quite a bit faster than Typescript.
- I haven't had a versioning problem in Go, and I can still compile and run old code. Typescript still beats Python in that respect, but Go wins stability.
And I say this as someone who really likes Typescript. It's a blessing for frontend browser work.
- sapiogram 2y ago> - A Go program runs single-threaded, unless you explicitly tell it not too, so I don't quite see that as a plus for Typescript. I don't think this is a fair comparison. Almost all software needs some kind of concurrency, and multi-threading is the only way to do concurrency in Go. For example, the http server in Go's stdlib runs each request in its own goroutine, which I guess you technically asked for, but also can't be avoided.
- tgv 2y agoThat means you think it's a good idea that a JS/TS server handles everything on a single thread, which doesn't sound like an advantage. BTW, you can also start multiple processes in go instead of go routines. There's probably a Worker-like library for it.
- GraduateDescent 2y agoIf you want TS-supported deserialization, just use runtime schema validation. I don't see the issue. It's dead-simple and is the way everyone does it.
- tgv 2y agoSure that's good advice, but it was a comparison of language features.