4 ms·
It's a bad look for both C# and TypeScript. Anybody starting a new code base now would be looking for ways to avoid both and jump right to Go.
by jay_kyburz 2y ago
It's a bad look for both C# and TypeScript. Anybody starting a new code base now would be looking for ways to avoid both and jump right to Go.
- bdangubic 2y agoif I had to use Go I’d change my career and go do some gardening :)
- ricardobeat 2y agoI'd probably have said the same 5 years ago, it's surprising how easy you change sides once you actually use it in a team.
- bdangubic 2y agoI was mostly joking… some of the most amazing shit code-wise I have seen in “non-mainstream” languages (fortran leads the way here)
- bbkane 2y agoI actually really enjoy Go. Sure it has a type system I wish was more powerful with lots of weird corners ( https://100go.co/ https://100go.co/ ), but it also has REALLY GOOD tooling- lots of nice libraries, the compiler is fast, the editor tooling is rock solid, it's easy to add linters to warn you about many issues (golangci-lint), and releasing binaries and updating package repositories is super nice (Goreleaser).
- keyle 2y agoI had to, and I do think a lot about gardening these days...
- zeroc8 2y agoI like Anders'answer there. "But you can achieve pretty great things with it".
- saturn_vk 2y agoBecause it's so easy that you'd have a lot more time for gardening?
- moogly 2y agoIf they're writing (actually porting) a _compiler_, perhaps.
- sethaurus 2y agoI'm struggling to understand how this is a bad look for Typescript. Do you mean that the specific choice of Go reflects poorly on Typescript, or just the decision to rewrite the compiler in a different non-TS language? If it's the latter, I think the pitch of TS remains the same — it's a better way of writing JS, not the best language for all contexts.
- jay_kyburz 2y agoI think a lot of folks downplay the performance costs for the convenience of a shared code-base between the front and backend. If the TS team is getting a 10x improvement moving from TS to Go, you might imagine you could save about 10x on your server cpu. Or that your backend would be 10x more responsive. If you have dedicated team for front and back anyhow, is a 10x slow down really worth a shared codebase?
- osigurdson 2y agoGo doesn't run in the browser however (except WASM but that is different).
- deleted 2y ago[deleted]