Live data from Hacker News

The Deno Company

deno.com

11–20 of 446 posts

Re: The Deno Company

#11

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?

We use it for the hash module in our standard library for example: https://deno.land/std@0.91.0/hash. The wasm version is magnitudes faster than a pure JS implementation. Another example is sqlite, running in WASM: https://deno.land/x/sqlite@v2.4.0. Fully sandboxed sqlite :-)

Re: The Deno Company

#12

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?

You can write in other languages beyond JavaScript or TypeScript and generate WebAssembly. This means that say someone wrote a nice library or utility in C# you can compile that C# down to WebAssembly and use that library or utility in JavaScript or TypeScript (or anything else that can access WebAssembly).

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

#13
post #6

congrats, i guess but not a fan of the VC route, we all know how this ends.

Which route on an independent MIT licensed project would you suggest?

It is matter of time until they release a proprietary version which is better than the MIT version.

Chrome vs chromium etc

Re: The Deno Company

#14
post #13
post #6

Earlier quoted context omitted.

Which route on an independent MIT licensed project would you suggest?

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

Re: The Deno Company

#15
Happy to see Deno get some financial backing!

I'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

#16
Excited to see a commercial company centered around the TypeScript ecosystem (both server and client) and betting on WebAssembly. Any successful Open Source must provide commercial value to become sustainable. Funnily enough that assures its longevity long term.

Keep 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.…

[flagged]

Re: The Deno Company

#19
post #13

Earlier 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

Yes, but Facebook said it will not monetize WhatsApp, and something similar when they bought WhatsApp Instagram.

We all know how that turned out to be

History repeats itself, the above two are the recent incidents that comes to my mind

Post reply on HN