4 ms·

> Although I must admit that I wouldn't use TypeScript in the backend for the projects we work one Can u elaborate on that? Why is TypeScript not suited for so

• renke1 6y ago
  For us particular, we heavily rely on fat frameworks like Spring (and sometimes Java EE) and there is nothing like that in TypeScript/JavaScript world. It boils down to not having classpath scanning, reflection and annotations in TypeScript, I guess. I don't want to defend these frameworks, though, they certaintly have their flaws, but it is what we use and it is often also what is teached in Germany. We also follow a domain-driven design approach for which we not yet have found a good way to implement in TypeScript (at least not on the "tactical" level). Edit: Also, people don't grok asynchronicity ;)
• caoilte 6y ago
  last time I was working in Typescript (a year) ago, the date/time libraries were still disappointing and precision math libraries were very way too cumbersome. Both are well solved problems on the JVM and in other languages.
  • dvlsg 6y ago
    Luxon makes for a good date lib stop gap while tc39 works on something built-in that is (hopefully) a bit nicer. https://moment.github.io/luxon/ https://moment.github.io/luxon/ https://tc39.es/proposal-temporal/docs/ https://tc39.es/proposal-temporal/docs/
• ragnese 6y ago
  For me, it's the Node ecosystem. The probability of even popular libraries having really basic bugs is way too high.