this post was submitted on 17 Sep 2024
295 points (99.3% liked)
Programming
17476 readers
199 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 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
If it's such a problem, maybe we just collectively move on to ES or TypeScript nomenclature?
Typescript and JavaScript are different languages and the distinction is important, especially because the two are used in conjunction with each other.
Especially because TypeScript compiles down to ~~JavaScript~~ JS
Yeah but why would you ever use javascript instead of typescript.
Don't answer that. 😂
Because I'm a browser and I can't read typescript.
For an application? Never. I'd still use it for something very small like a build script where the hassle of separate compile and run stages makes the whole thing a hassle to use. That might change now, though, since I think Node has gained the ability to execute Typescript directly.
Been using vite for a while and haven't had to think about it.
Glad node is catching up. But it'd spare even more headaches if it natively supported ES6 modules
The article mentions that the letter indicated intent to petition with the USPTO to cancel the Javascript trademark due to abandonment. Hopefully that is successful since that seems to be the best outcome short of Oracle willingly forfeiting it.