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

Deno 1.10 Release Notes

deno.com

Post reply on HN
Print view View original

51–60 of 157 posts

Re: Deno 1.10 Release Notes

#51

Post by vagrantJin »

tarruda wrote: post #35
echopom wrote: post #8

Still not tempted by Deno to be honest. All the problem that currently exist in Node are being ported to Deno straight up. The built-in apis provided by Node.JS are almost non-existent... hence most of them are buggy and quiet tedious to use , it's why the community has created thousands of packages to resolve those issues. Here I don't see how Deno is solving this , all the APIS seems again so barebone.. instead of…

> Here I don't see how Deno is solving this , all the APIS seems again so barebone.. instead of having 1000+ dependency from NPM you'll have 1000+ dependency from remote URL With Deno you can already do a lot with only what is provided by the main executable. Here's a subset of the available subcommands: bundle: Bundles JS. While it doesn't do everything that webpack does, it already provides enough to deploy SPAs. c…

> Starting a few of years ago, I don't even consider the possibility of creating a Javascript project without using Typescript as the main ...

The truth value of this statement is suspect but..

In any case, why should typescript be the default when it compiles to JS? Why shouldn't js be the default in a js framework?

Re: Deno 1.10 Release Notes

#52

Post by jackosdev »

tarruda wrote: post #35
echopom wrote: post #8

Still not tempted by Deno to be honest. All the problem that currently exist in Node are being ported to Deno straight up. The built-in apis provided by Node.JS are almost non-existent... hence most of them are buggy and quiet tedious to use , it's why the community has created thousands of packages to resolve those issues. Here I don't see how Deno is solving this , all the APIS seems again so barebone.. instead of…

> Here I don't see how Deno is solving this , all the APIS seems again so barebone.. instead of having 1000+ dependency from NPM you'll have 1000+ dependency from remote URL With Deno you can already do a lot with only what is provided by the main executable. Here's a subset of the available subcommands: bundle: Bundles JS. While it doesn't do everything that webpack does, it already provides enough to deploy SPAs. c…

Oh yeah forgot about built in TS, didn't even know about the build tools. Interesting, might have to give it another run

Re: Deno 1.10 Release Notes

#53

Post by nindalf »

e12e wrote: post #39
Cthulhu_ wrote: post #17

Earlier quoted context omitted.

I'm pretty confident we'll see a JS engine written in Rust at some point in the future, it'll just take a very long time to get parity with V8 and will likely introduce its own slew of issues.

I rather imagine we'll see a wasm vm/runtime in rust, and a typescript/js to wasm compiler written in typescript...

> I rather imagine we'll see a wasm vm/runtime in rust

Like Wasmtime? https://github.com/bytecodealliance/wasmtime

Re: Deno 1.10 Release Notes

#55

Post by hackerbrother »

echopom wrote: post #8

Still not tempted by Deno to be honest. All the problem that currently exist in Node are being ported to Deno straight up. The built-in apis provided by Node.JS are almost non-existent... hence most of them are buggy and quiet tedious to use , it's why the community has created thousands of packages to resolve those issues. Here I don't see how Deno is solving this , all the APIS seems again so barebone.. instead of…

It might catch on, it might not. Not everyone has to like it.

I personally do like it a lot. I think of it as Node.JS with a better organized core (with the benefit of hindsight), use of browser APIs whenever possible, and built in Typescript. I think it might catch on once we have some mature MySQL, Express.js, etc libraries.

I know seeing popular tools be rewritten from scratch is tiresome, but I don't think it's unreasonable in this case given that Node.JS and Deno mostly get their JS implementation from a separate program: V8. In that sense, Deno isn't throwing all of Node.JS away. It's just a different attempt to make V8 a command line tool.

And of course, competition is good. Maybe Typescript will become more convenient in Node because of Deno.

Additionally: as someone who uses Linux in their day to day job, I think it's a phenomenal scripting tool and replacement / supplement for Perl / Python. I mentioned this in a comment here the other day, but with this short wrapper, you can execute a bunch of SSH commands simultaneously using the Promise.all JS function (familiar to web devs). Just an example of a cool thing you can do with Deno scripting. https://github.com/gpasq/deno-exec

Re: Deno 1.10 Release Notes

#56

Post by tarruda »

vagrantJin wrote: post #51
tarruda wrote: post #35

Earlier quoted context omitted.

> Here I don't see how Deno is solving this , all the APIS seems again so barebone.. instead of having 1000+ dependency from NPM you'll have 1000+ dependency from remote URL With Deno you can already do a lot with only what is provided by the main executable. Here's a subset of the available subcommands: bundle: Bundles JS. While it doesn't do everything that webpack does, it already provides enough to deploy SPAs. c…

> Starting a few of years ago, I don't even consider the possibility of creating a Javascript project without using Typescript as the main ... The truth value of this statement is suspect but.. In any case, why should typescript be the default when it compiles to JS? Why shouldn't js be the default in a js framework?

I don't understand what you mean by "default". Deno simply provides a builtin compiler which allows it to run Typescript transparently. Clearly Deno also supports JS out of box.

Re: Deno 1.10 Release Notes

#57

Post by seumars »

jeswin wrote: post #31
echopom wrote: post #8

Still not tempted by Deno to be honest. All the problem that currently exist in Node are being ported to Deno straight up. The built-in apis provided by Node.JS are almost non-existent... hence most of them are buggy and quiet tedious to use , it's why the community has created thousands of packages to resolve those issues. Here I don't see how Deno is solving this , all the APIS seems again so barebone.. instead of…

> Ryan is the kind of guy that gets obsessed over ONE THING and goes berserk for 5 years on that topic until he overdose and quit abruptly. My problem with that statement is: if you knew him personally it's unlikely you'd have said it. And if you didn't, do you have enough samples to be sure he's 'that kind of guy'? Or are you extrapolating from N=1?

There’s something funny in talking about “samples” to sound smarter.

Re: Deno 1.10 Release Notes

#58

Post by azangru »

intellix wrote: post #43

How is the built in testing? I'm a bit wary because Jest is so good and wonder if it can compete on every front it's baking in. It reminds me of Angular coming with it's own Router, Forms, Animations and then since they're provided officially, alternatives don't get created and then the half of the team leaves and the packages are abandoned.

> How is the built in testing?

Much more minimalist than Jest. Very similar to Node's built-in testing [0].

- I don't believe the test environment is recreated between test files

- No way to mock imported modules, as far as I understand. I don't believe the built-in testing has any mocking or spying functionality at all

- No describe/it/expect syntax that Jest inherited from Jasmine (I am not sure where it came from initially — was it from RSpec?)

- The above means that there is no nesting of test blocks

- No setup or teardown functions (beforeAll, beforeEach, afterAll or afterEach)

On the other hand, it's fast. And it doesn't swallow up console logs, like Jest can do. No magic to it at all.

[0] - https://nodejs.org/dist/latest-v14.x/docs/api/assert.html

Re: Deno 1.10 Release Notes

#59

Post by littlecranky67 »

Cthulhu_ wrote: post #17
otabdeveloper4 wrote: post #5

Earlier quoted context omitted.

V8 is written in C++, not Rust.

I'm pretty confident we'll see a JS engine written in Rust at some point in the future, it'll just take a very long time to get parity with V8 and will likely introduce its own slew of issues.

I don't see any benefits (for me, the user) if its written in Rust. Yes, Rust has nice features for more security+stability for the developer, but just because a JS Engine would be written in Rust wouldn't mean its automatically better than V8. It's not the programming language that gives the edge in this case, it is the amount of time, sweat and grease that went into V8. And other engines would have a long way to come.

Re: Deno 1.10 Release Notes

#60

Post by noseratio »

hackerbrother wrote: post #55
echopom wrote: post #8

Still not tempted by Deno to be honest. All the problem that currently exist in Node are being ported to Deno straight up. The built-in apis provided by Node.JS are almost non-existent... hence most of them are buggy and quiet tedious to use , it's why the community has created thousands of packages to resolve those issues. Here I don't see how Deno is solving this , all the APIS seems again so barebone.. instead of…

It might catch on, it might not. Not everyone has to like it. I personally do like it a lot. I think of it as Node.JS with a better organized core (with the benefit of hindsight), use of browser APIs whenever possible, and built in Typescript. I think it might catch on once we have some mature MySQL, Express.js, etc libraries. I know seeing popular tools be rewritten from scratch is tiresome, but I don't think it's u…

Totally this, and not just for basic shell tasks but also as as scripting tool for CI/CD pipelines.
Post reply on HN