News for hackers. Stuff that matters.
Re:Kotlin 1.4 by tejinderss on Tuesday August 18, 2020 @05:34AM (#24196785)
> 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 some projects?

Re:Kotlin 1.4 by renke1 on Tuesday August 18, 2020 @06:13AM (#24196992)
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 ;)

Re:Kotlin 1.4 by caoilte on Tuesday August 18, 2020 @06:38AM (#24197136)
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.
Re:Kotlin 1.4 by dvlsg on Tuesday August 18, 2020 @11:02AM (#24199474)
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://tc39.es/proposal-temporal/docs/

Re:Kotlin 1.4 by ragnese on Tuesday August 18, 2020 @01:05PM (#24201208)
For me, it's the Node ecosystem. The probability of even popular libraries having really basic bugs is way too high.