| ▲ | Exoristos 3 hours ago | |
Seeing these graphs of astounding performance gains with less memory requirements makes one wonder, Why am I using server-side TypeScript and not Go? | ||
| ▲ | thunderfork 11 minutes ago | parent | next [-] | |
Whether the performance difference between Go and JS (via node or whatever) matters depends on your use case - it definitely matters for the TS compiler, but it might not matter at all for your CRUD app. | ||
| ▲ | semiquaver 2 hours ago | parent | prev | next [-] | |
For one, you’re not using TypeScript server-side. Whatever execution engine you are using is executing transpiled or JavaScript. And yeah, I don’t know who in their right mind is starting projects in TS/JS/python these days except when they don’t have an option. | ||
| ▲ | recursive an hour ago | parent | prev | next [-] | |
This is build-time performance, not run-time. | ||
| ▲ | throw310822 2 hours ago | parent | prev | next [-] | |
Because you can share types and even modules with your frontend project? Because for applications that aren't CPU-intensive it makes almost no difference? Because you are familiar with it and like it? Because of the humongous amount of libraries? | ||
| ▲ | Scarbutt 2 hours ago | parent | prev [-] | |
Because it’s easier to work with one main language if you can get away with it. | ||