Live data from Hacker News

Deno Joins TC39

deno.com

101–110 of 158 posts

Re: Deno Joins TC39

#101
post #96

Earlier quoted context omitted.

Is there some proposal for making the type syntax valid? No type checking just JavaScript parsing code with types and ignoring it.

How will Deno react if that happens?

Deno will behave just like Chrome or Firefox would: we ignore the checks when running your code. We would have a `deno check` subcommand to perform a typecheck. You could optionally run this automatically before a `deno run` by passing a `--check` flag.

Re: Deno Joins TC39

#102
post #73

Earlier quoted context omitted.

I am not aware of any specific proposals right now. There was some talk a while back about supporting SRI hashes inside of an import map, but that sorta dissolved. For Deno at least you can use a `lock.json` file with the `--lock` and `--lock-write` flags: https://deno.land/manual/linking_to_external_code/integrity_...

There's an issue for that to be added as part of import assertions https://github.com/tc39/proposal-import-assertions/issues/11...

I don't think that's going to fly because it's in-band.

Re: Deno Joins TC39

#103
post #22
post #12

Earlier quoted context omitted.

Will there be a Deno equivalent of Electron?

Aaron@Deno here, we've been exploring something with the Tauri team but don't have a concrete release on the roadmap since we're focusing on other priorities. I believe an Electron alternative is an important part of the Deno stack, so hopefully we'll ship a first iteration next year.

Why not PWAs?

Re: Deno Joins TC39

#104
post #84

Earlier quoted context omitted.

Yes, this would be great, and it will probably happen eventually. This is something we want to work on soon - expect something in the coming weeks.

Since TS/Deno has native support for JSX syntax, do you think Browsers will eventually support it as well?

No, I don't think so. JSX is too proprietary and not specified well enough. It is also rather ambiguous.

If you want a "no compile" JSX:

```jsx

const x = hello;

// is the same as

const x = h("div", { color: "red" }, "hello");

```

Re: Deno Joins TC39

#105
post #97
post #86

> As TypeScript is a core part of the Deno ecosystem, we are also very interested in pushing for even closer alignment of TypeScript and JavaScript in the future. I've wondered why the frontend community hasn't gotten together and said, "The next version of JavaScript - is TypeScript!" I've been using TypeScript for five years professionally now and cannot understate how much easier it has made large frontend (not ju…

Types in TypeScript are great but if JavaScript ever wants to add types it has to be something like a real programming language types in which you can use types in runtime as well. Like in a catch clause I can assert the type of the error and do things with it once that assertion is done. Many other useful things when types space and runtime space are not totally separate. ES4 was the first shot at adding types to Ja…

"real programming language types"

There are a few languages where types only exist (for the most part, though with exceptions and hacks here and there) at compile-time, like Rust, C++ or even Haskell IIRC.

Re: Deno Joins TC39

#106

Hey - I am Luca Casonato, Deno's new delegate at TC39. I am happy to answer any questions you all might have :-)

Do you have discussions about not adding too many features to JavaScript? It's already quite complex for beginners.

This is always a consideration when adding new features. It is however also important to keep the language up to date with other modern languages. If you don't innovate, you die. There is always a cost/benefit calculation to be made.

Re: Deno Joins TC39

#107
post #81

Hey - I am Luca Casonato, Deno's new delegate at TC39. I am happy to answer any questions you all might have :-)

When cross platform windowed WebGPU on Deno? It would be interesting for many kinds of apps.

We are not sure about windowed WebGPU right now. We will try to come up with some form of "Deno Desktop" next year, but I have no real ETA for that.

Re: Deno Joins TC39

#108
post #86

> As TypeScript is a core part of the Deno ecosystem, we are also very interested in pushing for even closer alignment of TypeScript and JavaScript in the future. I've wondered why the frontend community hasn't gotten together and said, "The next version of JavaScript - is TypeScript!" I've been using TypeScript for five years professionally now and cannot understate how much easier it has made large frontend (not ju…

TypeScript is great and everything, but Microsoft owns the standard and the single functioning checker, and haven't published a specification or even a grammar.

The TypeScript checker/compiler is Apache 2.0 licensed, so I'm not sure there's room to complain, unless you disagree with the direction they're taking the project:

https://github.com/microsoft/TypeScript/blob/main/LICENSE.tx...

Re: Deno Joins TC39

#109
post #46

Earlier quoted context omitted.

I hope the pace will accelerate. The real questions is what functions we need though. Some candidates that I would love to see are better helper functions on iterators, and Uint8Array base64/hex. Most of the "standard library" in most languages is related to IO, and for JS is dependant on the host (the web, Deno, Node) so not something TC39 will touch directly. Do you have ideas for standard library functions that yo…

I often miss map, reduce and filter on iterators, though this is already a stage 2 proposal: https://github.com/tc39/proposal-iterator-helpers .

This is definitely something I am interested in pushing too. Iterators have not gotten the love they deserve.

Re: Deno Joins TC39

#110
post #46

Earlier quoted context omitted.

I often miss map, reduce and filter on iterators, though this is already a stage 2 proposal: https://github.com/tc39/proposal-iterator-helpers .

This is definitely something I am interested in pushing too. Iterators have not gotten the love they deserve.

That's great to hear! Congratulations and thank you for your work.
Post reply on HN