this post was submitted on 14 Mar 2025
47 points (100.0% liked)
Programming
19177 readers
368 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Eh, not entirely. Typescript will build faster and the text editor can parse it quicker but once it hits the browser no speed is gained. It's kinda stated in the article but it dances around it quite well I wouldn't blame you for missing it.
This just makes transpilation quicker along with some other benefits while working with it in editor. It's still just JavaScript in the end this just gets it there quicker. Still very cool though.
Yeah, the article comes off as needing so much context that the article itself is sus. Like
… which is referencing an implementation of Doom in the TS type system. It's a funny idea, but an arbitrary reader who doesn't know about that and doesn't bother clicking through will get a very wrong impression.
The reimplementation (which they've done partially automated; Go apparently lets them do a very simple translation while Rust or C# would require more work to fit) should be a boon for TS devs, but not noticeable for those who just run stuff that happens to be written in TS.
Would be kinda interesting to see the effect if stuff targeted
denorather thannode, though.