A space to discuss and keep up software development and manage your software career
An inclusive community for gaming enthusiasts
News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more.
From composing and gigging to gear, hot music takes, and everything in between.
Discussing AI software development, and showing off what we're building.
A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here
Movie and TV enthusiasm, criticism and everything in-between.
Memes and software development shitposting
Web design, graphic design and everything in-between
A community of golfers and golfing enthusiasts
Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike
For engineers building software at scale. We discuss architecture, cloud-native, and SRE—the hard-won lessons you can't just Google
Discussing the core forem open source software project — features, bugs, performance, self-hosting.
A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis.
A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other.
A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more.
This is a simple question.
Typescript compiles to Javascript, so it'll die along with it. 😅
Well, no.
Typescript is technically Javascript's son, so if the parents died, it would just be an orphan.
So, there is TypescriptToLua, it transpiles Typescript to Lua instead of JS. So if JS become too sucky and unusable, basically dead, we can use that.
And we can also make an engine that runs runtime Typescript (that would mean run-time type-checking etc), kinda like V8 but Typescript.
I see, I didn't know of these options for Typescript! Especially TypescriptToLua sounds interesting, since that could make Lua the replacement for JS while still retaining TS.
Not with Dino around. If Dino replaces the JavaScript engine in a browser, that would be TypeScript directly in the browser.
I remember the Tcl/Tk plugin for Netscape’s browser. That was fun!
You mean Deno?
yea, I’m a lousy speller. But, most engineers are.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is a simple question.
Typescript
Typescript compiles to Javascript, so it'll die along with it. 😅
Well, no.
Typescript is technically Javascript's son, so if the parents died, it would just be an orphan.
So, there is TypescriptToLua, it transpiles Typescript to Lua instead of JS. So if JS become too sucky and unusable, basically dead, we can use that.
And we can also make an engine that runs runtime Typescript (that would mean run-time type-checking etc), kinda like V8 but Typescript.
I see, I didn't know of these options for Typescript! Especially TypescriptToLua sounds interesting, since that could make Lua the replacement for JS while still retaining TS.
Not with Dino around. If Dino replaces the JavaScript engine in a browser, that would be TypeScript directly in the browser.
I remember the Tcl/Tk plugin for Netscape’s browser. That was fun!
You mean Deno?
yea, I’m a lousy speller. But, most engineers are.