Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Deno Joins TC39

deno.com

Post reply on HN
Print view View original

81–90 of 158 posts

Re: Deno Joins TC39

#81

Post by bartq »

lucacasonato wrote: post #2

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.

Re: Deno Joins TC39

#82

Post by tempodox »

FragenAntworten wrote: post #47
lucacasonato wrote: post #14

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…

'enumerate', as in Python. 'clamp' and 'sortBy', as in Lodash. Set methods for union, intersection, difference, etc.

Re set operators: For completeness' sake there would have to be a way to specify how set elements are to be tested for equality.

Re: Deno Joins TC39

#83

Post by speedgoose »

lucacasonato wrote: post #2

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.

Re: Deno Joins TC39

#84

Post by ducaale »

lucacasonato wrote: post #58
egeozcan wrote: post #52

Earlier quoted context omitted.

could you imagine that some JS proposal adds the ability to ignore TS-like type annotations to the engines, so we don't even have to strip them? this may help development heavily, also making the browser and deno nearly identical environments.

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?

Re: Deno Joins TC39

#85

Post by runarberg »

tarjei_huse wrote: post #57
lucacasonato wrote: post #14

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 miss being able to create a hash from an array in a quick way. You always end up with let bar = [{id: zz, }, {id: y},...] let foo = {} bar.forEach(v => foo[v.id] = v) I'd love to have something like: let foo = bar.toMap(v => [v.id, v])

    let foo = Object.fromEntries(bar.map((v) => [v.id, v]));

Re: Deno Joins TC39

#86

Post by disease »

> 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 just Web, but mobile and desktop) projects. Surely enough thought and work has been put into TypeScript to make it the next standard.

Re: Deno Joins TC39

#87

Post by adamddev1 »

lucacasonato wrote: post #80
adamddev1 wrote: post #78

Earlier quoted context omitted.

Or how about TCO (tail-call optimization)? Please pretty please!

TCO is something that specific JS engines need to implement. It is implemented in JSC (Safari), but not in V8 or SpiderMonkey. Also see https://v8.dev/blog/modern-javascript#proper-tail-calls . As this is an engine feature rather than a spec thing, there is nothing me (or any other TC39 delegate) can do.

Oh yes, I see, that's true. Thanks for the explanation.

Re: Deno Joins TC39

#88

Post by brundolf »

hajile wrote: post #68
lucacasonato wrote: post #2

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

Are you going to push for records and tuples? Eich was pushing for them in 2011 and they still haven't arrived. https://brendaneich.com/2011/01/harmony-of-my-dreams/

I haven’t read the full post, but what’s the benefit of adding language support for records and tuples at this point? My understanding is that engines already optimize the objects/arrays version of those concepts pretty well, and TypeScript enforces the semantics on the dev side.

Re: Deno Joins TC39

#89

Post by dcgudeman »

disease wrote: 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…

Because then ability for typescript to be agile would be destroyed. JavaScript can’t be changed as easily as typescript.

Re: Deno Joins TC39

#90

Post by hajile »

adamddev1 wrote: post #78
hajile wrote: post #68

Earlier quoted context omitted.

Are you going to push for records and tuples? Eich was pushing for them in 2011 and they still haven't arrived. https://brendaneich.com/2011/01/harmony-of-my-dreams/

Or how about TCO (tail-call optimization)? Please pretty please!

Proper tail calls are ALREADY part of the spec.

Google and Mozilla simply chose to ignore the spec.

Post reply on HN