6 ms·
> but I still got folks on Twitter telling me to "just use TypeScript", This type of behavior is exactly the reason why I think the existence of Typescript add
by timdaub 6y ago
> but I still got folks on Twitter telling me to "just use TypeScript",
This type of behavior is exactly the reason why I think the existence of Typescript adds downsides to being a JS dev.
Saying "just use TS" is of equal value as saying: "just use Assembly" or "just use Dart". It has no value.
First an foremost this type of logical behavior is a problem that needs to be adressed in JavaScript. The dynamically typped language that is embedded into every major browser. A heuristic will have to be discovered by JS devs. Or TC39 will have to extend the standard.
Ultimately, it then comes down to a contexual personal choice of using TS over JS.
When it comes to separation of concerns, I can recommend reading this essay by Dijkstra: https://www.cs.utexas.edu/users/EWD/transcriptions/EWD04xx/EWD447.html https://www.cs.utexas.edu/users/EWD/transcriptions/EWD04xx/E...
- ragnese 6y agoPersonally, I'm not a fan of TypeScript anyway. JavaScript is a lost cause to me. I'm not a full time JS Dev, so every time I have to touch one of our Node projects at work, I mentally prepare myself for very slow dev speed (ironic, considering the arguments that dynamically typed, loosey goosey, language speed you up) and frustrating bugs around `this`, mixed up function arguments, forgetting to await promises returned from functions, etc. But TypeScript really doesn't actually help that much compared to an IDE that understands JSDoc. Its type system is unsound and it's too accommodating of JavaScript's nonsense. If I ever start a new project that just has to run on Node, I'd probably try one of these languages that transpiles to JS, but is totally different, like Clojure or OCaml.