Re:TypeScript is terrible for library developers
by int_19h on Tuesday August 23, 2022 @05:41PM
(#32571939)
> It fits in the JavaScript spirit of "we will make it work" which I love.
Do you also use == and != for comparisons by default?
Re:TypeScript is terrible for library developers
by robbiejs on Wednesday August 24, 2022 @02:59AM
(#32575778)
Check out the library, it's not that bad ;-)
Re:TypeScript is terrible for library developers
by WorldMaker on Wednesday August 24, 2022 @01:29PM
(#32582787)
> Other major thing that made me decide to develop in es6 instead of typescript was compilation times. After a ctrl+s it had to compile ts to js for 10 seconds, which is annoying for me, as i like to check & test every minor code change.
Typescript has a --watch mode that compiles as you work. Most test runners also often have a --watch mode. Test runners that support Typescript directly don't even need Typescript's --watch to be running as they'll do both, compile and test in a single step as you save. Anecdotally, the time it takes to run tests dwarfs any Typescript compile times and in a --watch mode of a test runner there's almost zero difference in the time it takes to watch ES2015+ tests or Typescript tests.
grid.selectRows(2) // index grid.selectRows([3,5]) // range grid.selectRows([[1,2],[4,6]]) // multiple ranges
It fits in the JavaScript spirit of "we will make it work" which I love.
Other major thing that made me decide to develop in es6 instead of typescript was compilation times. After a ctrl+s it had to compile ts to js for 10 seconds, which is annoying for me, as i like to check & test every minor code change.