by caspervonb on 5/12/21, 6:28 AM with 147 comments
by echopom on 5/12/21, 8:29 AM
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.
by the_duke on 5/12/21, 10:25 AM
But I also was quite skeptical of their dependency model with plain url imports.
With the current implementation you end up with a half-baked import map that's essentially a poor mans package.json, but without any of the tooling that you'd expect. (like npm upgrade, npm outdated)
It recently dawned on me what they are going for: a "cloud native" computing platform that doesn't require builds and packaging. Targeting both Javascript and WASM.
I do believe there is quite a lot of promise in the project. The tooling can improve. It'll be interesting how things evolve.
by CraigJPerry on 5/12/21, 8:10 AM
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.
by okhuman on 5/12/21, 8:35 AM
by 8K832d7tNmiQ on 5/12/21, 8:06 AM
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.
by davnicwil on 5/12/21, 8:38 AM
It seems very in line with the model of deno as an edge compute runtime - esentially ephemeral cache on the edge - I wonder what usecases will emerge for this?
by redleader55 on 5/12/21, 10:43 AM
Each team will have different problems when it comes to scaling, running tests in parallel - sometimes on the same machine, sometimes on multiple machines, e2e tests vs unit-tests, etc. This looks like a problem you solve in a library, not something to add in the core.
by intellix on 5/12/21, 10:21 AM
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.
by jimmont on 5/12/21, 6:28 PM
by sam_goody on 5/12/21, 12:37 PM
As long as Electron has no plans to support Deno, it will be WAY behind in traction.
/useless prediction
by ledgerdev on 5/12/21, 1:49 PM
by paxys on 5/12/21, 6:28 PM
by Graffur on 5/12/21, 12:29 PM
by ralusek on 5/13/21, 8:10 AM
by domano on 5/12/21, 11:50 AM
by kumarvvr on 5/12/21, 1:52 PM
I love to explore new stuff in programming. Have done with Python, Java, JS (Node), React, Angular, Vue, etc.
Deno just doesn't cut it.
by caspervonb on 5/12/21, 11:11 AM
by sanxiyn on 5/12/21, 11:07 AM
by DrFell on 5/12/21, 2:16 PM