Deno 1.10 Release Notes
deno.com
Deno 1.10 Release Notes
1–10 of 157 posts
Re: Deno 1.10 Release Notes
#2I'm still waiting for abortable fetch feature, since I have to deal with some services that have unstable network connection and often got stuck and never drop their connection.
Is there any progress over this one? Last time I heard, they still have to wait till rusty_v8 got matured enough for this feature to be available.
Re: Deno 1.10 Release Notes
#3I didn’t know what deno was.
It’s a typescript native alternative to nodejs that adopts the browser security model, replicates the golang standard library rather than node’s and is written in Rust.
Re: Deno 1.10 Release Notes
#4I didn’t know what deno was. It’s a typescript native alternative to nodejs that adopts the browser security model, replicates the golang standard library rather than node’s and is written in Rust.
Not only adopts the browser security model, but more broadly adopts browser APIs.
Re: Deno 1.10 Release Notes
#5I didn’t know what deno was. It’s a typescript native alternative to nodejs that adopts the browser security model, replicates the golang standard library rather than node’s and is written in Rust.
V8 is written in C++, not Rust.
Re: Deno 1.10 Release Notes
#6I didn’t know what deno was. It’s a typescript native alternative to nodejs that adopts the browser security model, replicates the golang standard library rather than node’s and is written in Rust.
V8 is written in C++, not Rust.
They're talking about deno, which _is_ written in Rust. https://github.com/denoland/deno
Re: Deno 1.10 Release Notes
#7Earlier quoted context omitted.
V8 is written in C++, not Rust.
They're talking about deno, which _is_ written in Rust. https://github.com/denoland/deno
Deno is a simple, modern and secure runtime for JavaScript and TypeScript that uses V8 and is built in Rust.
So it's probably a rust wrapper around a C++ project (unless they reimplement V8 in rust... )
Re: Deno 1.10 Release Notes
#8Still 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 having 1000+ dependency from NPM you'll have 1000+ dependency from remote URL with everything set at "read/write" because they need to read one file from your ".env" folder or perform an arbitrary post install process...
The way Ryan managed Node and how the ecosystem as turned to chaos because of is lack of vision and strategy make me not want to try any of it's tech again. 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.
I don't think that's how you manage a language , when I look at Zig I'm way more confident of what's being done that the current state of Deno...
Node.JS is one of my main language , but the ecosystem around it is an absolute disaster.
Re: Deno 1.10 Release Notes
#9[deleted]
Re: Deno 1.10 Release Notes
#10[deleted]