News for hackers. Stuff that matters.
Re:Deno will stop using TypeScript by kiliancs on Sunday June 21, 2020 @01:39PM (#23593651)
Working on half a million LOC TypeScript codebase. All strict flags up, low-2-digit team size. We don't really run into many problems. TypeScript is not perfect, but developer happiness and productivity have definitely increased since we adopted it, and defect rates have dropped significantly --while increasing the size of the team & working on more features.
Re:Deno will stop using TypeScript by yawboakye on Sunday June 21, 2020 @01:45PM (#23593702)
Think of the change as a statically compiled language writing parts of their runtime with assembly or unsafe pointers. It’s not an indictment of TypeScript.
Re:Deno will stop using TypeScript by kiliancs on Sunday June 21, 2020 @01:55PM (#23593782)
My first impression of the reasons in the design doc is that the change is not well justified, but I also see the point you make; my response, though, was to the direct parent comment.
Re:Deno will stop using TypeScript by thegreatpeter on Sunday June 21, 2020 @03:18PM (#23594569)
I have a hard time believing that. We have 10k lines of typescript and that take forever to compile compared to 5x more of the ReasonML code we have that compiles instantly
Re:Deno will stop using TypeScript by petersellers on Sunday June 21, 2020 @03:28PM (#23594646)
You have a hard time believing that their team experienced more happiness and productivity with TS...because your ReasonML code compiles a lot faster than your TS code?
Re:Deno will stop using TypeScript by kohtatsu on Sunday June 21, 2020 @03:43PM (#23594764)
I've actually been (very) wary of adopting TypeScript once I learned of the multi-second compile times, even for tiny projects.

I had actually been watching Deno in case they solved any of that.

Re:Deno will stop using TypeScript by goostavos on Sunday June 21, 2020 @06:07PM (#23595791)
They become really frustrating as the project grows in size. Personally, it becomes really difficult to maintain productivity. As compile times tick up, I start bouncing over to other tabs rather than just twiddling my thumbs starring at a terminal. Then I realize I've been on Reddit for a half-hour.

I recently watched this talk by Johnathan Blow[0] where he talks about quality of life in programming languages and spends a fair amount of time talking about compile times and their effects.

I think we collectively need to re-align on being performance focused. Tools are simultaneously amazing but crummy at the same time.

[0] https://www.youtube.com/watch?v=uZgbKrDEzAs&t=2s

Re:Deno will stop using TypeScript by kiliancs on Sunday June 21, 2020 @08:53PM (#23596558)
I don't love the compile times, but I'll also say with TypeScript I tend to check the browser that often. TS also means simpler refactoring, for example.

Note also: * type checks can run in parallel, so they won't block your other build block * the tsc has been making gradual improvements to performance and techniques to improve compilation and type checking * there are speedy alternatives to the TypeScript compiler (tsc) (eg: https://sucrase.io) for transpilation

Re:Deno will stop using TypeScript by ithrow on Sunday June 21, 2020 @05:43PM (#23595662)
Much faster compiles times sounds like a good reason to me ;)
Re:Deno will stop using TypeScript by kiliancs on Sunday June 21, 2020 @04:14PM (#23595030)
I wasn't comparing to ReasonML, which I'm convinced is a very good choice.