From the last paragraph: > But JavaScript and TypeScript scripts calling into WebAssembly code will be increasingly common. Why is WebAssembly a key concept here? How does Deno uses it?
The Deno Company
11–20 of 446 posts
Re: The Deno Company
#12From the last paragraph: > But JavaScript and TypeScript scripts calling into WebAssembly code will be increasingly common. Why is WebAssembly a key concept here? How does Deno uses it?
This is analogous perhaps to C# and F# within .NET currently. C# and F# have the same BCL (base common layer) so you can use C# code in F# and vice versa. WebAssembly is like that and much more.
Re: The Deno Company
#13Re: The Deno Company
#14Re: The Deno Company
#15I've been building my new multiplayer games website [1] with Deno over the last 4 months and apart from some minor growing pains, it's been a joy to use.
The lack of unnecessary package management, and the TypeScript-by-default approach makes Web dev much nicer. We're also using TypeScript on the client-side, relying on VSCode for error reporting. We use sucrase to strip the types just as we're serving the script files, so that there is no extra build time, it feels like TypeScript is Web-native and we can share typed code with the server.
[1] Not yet launched but we ran a preview past weekend with hundreds of players over WebSockets: https://twitter.com/MasterOfTheGrid/status/13757583007179735... - https://sparks.land
Re: The Deno Company
#16Keep up the great work Ryan, Bert & team. Exciting times!
Re: The Deno Company
#17> Extending web programming beyond the browser is not a novel idea. Indeed, we have done that with moderate success in our “Node.js” project. But over a decade later, we find server-side JavaScript hopelessly fragmented, deeply tied to bad infrastructure, and irrevocably ruled by committees without the incentive to innovate. As the browser platform moves forward at a rapid pace, server-side JavaScript has stagnated.…
Re: The Deno Company
#18Re: The Deno Company
#19Earlier quoted context omitted.
It is matter of time until they release a proprietary version which is better than the MIT version. Chrome vs chromium etc
The blog post specifically says that that will not happen
We all know how that turned out to be
History repeats itself, the above two are the recent incidents that comes to my mind