4 ms·
With many TS features making their way into JS, I've sometimes wondered if TS is to JS what Sass is to CSS. I currently rely on TS, but I now consider Saas harm
by chrisweekly 2y ago
With many TS features making their way into JS, I've sometimes wondered if TS is to JS what Sass is to CSS. I currently rely on TS, but I now consider Saas harmful [there being overlapping syntax w/ vanilla CSS].
- iainmerrick 2y agoWhat features are you thinking of? I hadn’t heard anything about TS types making their way into JS in any way (unless you count engines that can execute TS directly, but those just ignore the type syntax). That would be a massive change.
- chrisweekly 2y agohttps://www.totaltypescript.com/erasable-syntax-only https://www.totaltypescript.com/erasable-syntax-only https://tc39.es/proposal-type-annotations/ https://tc39.es/proposal-type-annotations/
- iainmerrick 2y agoHmm, I don’t think either of those warrants any concern about “TS features making their way into JS” or “overlapping syntax”. The first one is removing a TS feature that failed to make its way into JS, and the second is about explicitly carving out a space in the syntax so that you can use TS (or Flow!) in JS codebases without being locked into any particular tooling.