Static TypeScript: A Static Compiler for the TypeScript Language
1–10 of 57 posts
Re: Static TypeScript: A Static Compiler for the TypeScript Language
#2Are there any plans to release this?
Re: Static TypeScript: A Static Compiler for the TypeScript Language
#3Are there any plans to release this?
It already is.
From the parent link: https://github.com/microsoft/pxt/
Re: Static TypeScript: A Static Compiler for the TypeScript Language
#4Are there any plans to release this?
Already part of Microsoft MakeCode learn to code ecosystem. Read this blog for more details: https://www.microsoft.com/en-us/research/blog/rocket-fast-em...
Re: Static TypeScript: A Static Compiler for the TypeScript Language
#5Given that they're both TypeScript subsets with similar goals, how close is STS to AssemblyScript? And is WebAssembly also a planned or possible compilation target of STS?
Re: Static TypeScript: A Static Compiler for the TypeScript Language
#6This language is quite striking! TypeScript is a superset of JS but here we're going from the other direction. Make a language that is only the TypeScript extensions to JS, and drop all the JS parts.
No Object (!!), no Date, TypedArray, RegExp, almost all the mainstays are gone. It's Java 1.0: static offsets and vtables.
This feels like the beginning of TypeScript throwing its weight around. It has the momentum to supplant JS and this is an exploratory compatibility-breaking step.
Re: Static TypeScript: A Static Compiler for the TypeScript Language
#7I believe this will have major implications for the WebAssembly ecosystem.
It also makes me wonder how AssemblyScript will fit into the picture. Anyone from Microsoft/TypeScript can shed some light on future plans?
Re: Static TypeScript: A Static Compiler for the TypeScript Language
#8I believe this will have major implications for the WebAssembly ecosystem. It also makes me wonder how AssemblyScript will fit into the picture. Anyone from Microsoft/TypeScript can shed some light on future plans?
In its current state, Static TypeScript is a toy compared to AssemblyScript.
It doesn’t support much of the original TypeScript features, while AssemblyScript is getting pretty close to the original TypeScript.
AssemblyScript was also specifically designed to target WebAssembly. For example, it supports 64 bit types and has builtins that directly map to WebAssembly opcodes.
Static TypeScript would have to be repurposed as explicitly targeting WebAssembly in order to become a viable alternative.
And Static TypeScript is part of a set of projects with very different goals.
That being said, it could indeed be turned into something targeting WebAssembly. And unless Microsoft goes that route, it may happen as a fork. Still, I’m not sure of the benefits compared to AssemblyScript. I’d rather see Microsoft contribute to AssemblyScript.
Re: Static TypeScript: A Static Compiler for the TypeScript Language
#9See it in action:
Re: Static TypeScript: A Static Compiler for the TypeScript Language
#10I believe this will have major implications for the WebAssembly ecosystem. It also makes me wonder how AssemblyScript will fit into the picture. Anyone from Microsoft/TypeScript can shed some light on future plans?
In its current state, Static TypeScript is a toy compared to AssemblyScript. It doesn’t support much of the original TypeScript features, while AssemblyScript is getting pretty close to the original TypeScript. AssemblyScript was also specifically designed to target WebAssembly. For example, it supports 64 bit types and has builtins that directly map to WebAssembly opcodes. Static TypeScript would have to be repurpos…
Same. I’d like to analyze more time into the project, it seems is mainly for education proposes?
Either way, I hope Microsoft pushes AssemblyScript forward :)