69
u/vi_code Jun 21 '22
Never used deno. What makes it better than just using node?
158
u/Skhmt Jun 21 '22
It has several advantages, like native typescript, better packages, a better mascot, etc.
55
u/webstackbuilder Jun 21 '22
The dinosaur mascot clinched it for me. Native typescript and better packages, meh.
9
75
17
-23
u/Charuru Jun 21 '22
Stuff that have no effect on productivity for 99% of devs.
14
u/Swingline0 Jun 22 '22
The revisions to dependency management (the thing devs complain about Node the most) seem like a substantial improvement.
My understanding of the genesis of Deno is that the creator of Node (a dev) was plagued by his design decisions of Node which turned out to be flawed—Deno is his attempt at fixing them.
I'm pretty sure the intention is specifically to improve developer productivity and quality.
3
u/Charuru Jun 22 '22
Yes I'm fully aware, but actual problems arising from dependencies is like a fairly minor edgecase, more of a theoretical problem than an actual issue. There are like millions of projects using npm just fine.
10
u/Swingline0 Jun 22 '22
Good point. I've been a Node developer for 8 years and now that you mention it, I've never had any issues or heard any complaints about npm's availability/security. I've also never experienced dependency hell, peer dependency errors, the aggregate disk space consumed by our many recursive node_modules directories, or inconsistent module interfaces.
The introduction of ES module support into Node has been smooth sailing too. No issues whatsoever, as long as I use ESBuild, webpack, parcel, or browserify. After that babel, eslint, prettier, and typescript take care of the rest! It's been super painless, easy to maintain, and I know every one of my developers is comforted by knowing that each of these tools work in persistent harmony without ever causing distractions and confusion.
As a long standing enthusiast and evangelist of Node, it's weird that I forgot Node is perfect in every possible way and that we should resist change and only defend the things we understand—to consider alternatives is sacrilege and we should be condemned for questioning our chosen path.
We already made the right decision, once, so let's be smart and shit on anything else without saying anything intelligent or meaningful.
1
u/Charuru Jun 22 '22
ofc Deno is better, I use Deno too lol. But factually that stuff just doesn't matter to 99% of people.
0
Jun 21 '22
[deleted]
76
u/Michael_Pitt Jun 21 '22
We've had those posts for years
0
Jun 21 '22
[deleted]
29
u/mikeywayup Jun 21 '22
Corp: We need 10 years of Deno experience
11
u/reddit_ronin Jun 22 '22
For 30% under market value salary. Also please take this horrid code exam so my awkward mid-level dev, who created it, can flex in front of the rest of the team.
7
Jun 22 '22 edited Dec 07 '23
[removed] — view removed comment
10
u/crabmusket Jun 22 '22
Actually because Deno is an ecosystem fork, you don't need to deal with
@types, ESM support differences, etc etc etc.Don't get me wrong, I use ts-node and am not shipping Deno in production. But there are significant benefits to its approach.
14
Jun 22 '22 edited Jun 22 '22
It splinters the community to divert good developers to yet another pointless side quest.
Joking aside, it should have been a major breaking update to node.
0
90
u/techn007 Jun 22 '22
Looking for a seasoned Deno developer with at least 5 years experience of deploying deno projects to production
No "can do" attitude won't work here. I need this developer yesterday.
18
u/rk06 Jun 22 '22 edited Jun 22 '22
Sure. I know some javascript and how to Google, so i basically know deno as well. Hell I invested an hour of time on hackernews the day deno was out.
I am also pretty cheap. I am willing to work for $80k per month! No stock options or anything required Yay, i know its peanuts, but i care about job, not money and willing to make sacrifices.
Also additional sacrifices that I am willing to make. 100% WFH, so you don't need to have an office. I also am willing to work M1 MacBook 14" and apple 4k monitor and afew other necessary office equipments.
And since I like you, i am willing to join yesterday!! So, make sure to pay me from yesterday. Will start work right after getting equipment.
2
Jul 14 '22
lets not forget unlimited vacation, of which you must take at least 6 months out of the year off. In order to keep code quality top notch
7
7
u/pepsisugar Jun 22 '22
Entry level salary you say?
3
49
u/cfife_dawg Jun 21 '22
It's probably worth mentioning that it's not really 21M for Deno, but it's more for their cloud services that they are working along with Deno. Not saying that's a bad thing or anything though
18
u/Swingline0 Jun 22 '22
My first reaction is that it feels a bit "cart before the horse"
I really want Deno to succeed, it seems to be an improvement across the board for developer experience and workflow sanity.
Leading with cloud hosting or enterprise sponsorship seems to muddy the value and I'm worried it will inhibit Deno's acceptance and general adoption.
6
u/marchingbandd Jun 22 '22
I feel like the case for their clouds superiority is one of the clearest they have as a framework currently. Laid out as it is in that article it’s a strong yes. I see many benefits to deno, but this one feels like it has wings.
27
15
u/SquatchyZeke Jun 22 '22
I haven't kept up very well with Deno. It kind of seemed like a hipster alt to Node for a while and that's all I got from it. Seeing Netlify's partnership is painting Deno in a new light for me. And Deno Deploy seems really powerful. I think I'll use Deno in my next project; seems like it may be a good skill to have in the near future for JS devs
5
u/fixrich Jun 22 '22
As someone who has worked with Deno, there's nothing to learn. If you are familiar with Typescript and modern JavaScript standards, you already know it. All it provides is a more integrated workflow over Node. By all means build something with it but you won't find any groundbreaking changes.
The main reason we're seeing all these partnerships and funding rounds is they're chasing the rush for developer tooling VC.
3
u/eldnikk Jun 22 '22
All it provides is a more integrated workflow over Node.
Can you elaborate on this?
5
u/fixrich Jun 22 '22
Built in type checker, built in linter, built in testing (node has this now), a more comprehensive standard library and arguably a more prescriptive dependency and security workflow. You can get all this in node with arguably pretty standard options like eslint and npm but Deno makes a point of shipping it with the runtime
1
u/SquatchyZeke Jun 23 '22
Well that's good to know! How different are the APIs though? Like for I/O or crypto as some examples?
18
u/Rudxain 📚Librarian lol Jun 22 '22
I always felt like Deno was invisible. How come Deno is better than Node, yet people don't seem to push enough for a transition process to migrate Node projects to Deno? Or am I living under a rock and devs are actually doing this right now? I really wish Deno replaced Node, not necessarily to deprecate Node (I don't hate Node), but for a better JS development future
36
u/ndm250 Jun 22 '22
Deno is still new. They claim their standard modules aren't yet stable. Most probably shouldn't use deno in production.
6
u/Rudxain 📚Librarian lol Jun 22 '22
Oh... that's a serious problem. I thought Deno was essentially "ready to use"
29
u/Swingline0 Jun 22 '22
Lol I imagined you deploying some, newly Deno-fied, mission critical service as you read that comment.
"Oh, fuck"
17
1
u/Rudxain 📚Librarian lol Jun 22 '22
LMAO. I meant that it could be a problem for someone else. I'm currently not using Node, nor Deno, but I'm considering doing so in the future
2
u/glmdev Jun 22 '22
Yeah, tried to get into it for some personal projects a while back and kept hitting bugs/breaking changes in the standard modules. Hopefully that will clear up with time.
6
u/Swingline0 Jun 22 '22
I thought it was still just in its infancy, too.
The nature of this press release has me concerned... Like they're jumping to monetization before anyone is actually ready to use it.
The last meaningful news I remember hearing about Deno was that Ryan had made an early stage prototype of Deno that people could kick the tires on. I remember playing with it locally for a bit, it seemed pretty robust already but there was a lot of intentional messaging saying it wasn't production ready.
1
u/crabmusket Jun 22 '22
The last meaningful news I remember hearing about Deno was that Ryan had made an early stage prototype of Deno that people could kick the tires on
You can check out all the release notes for their post-1.0 versions if you want to see how they've been going recently!
0
Jun 22 '22
[deleted]
3
u/Swingline0 Jun 22 '22
I totally hear that. Not advocating for anyone working for free, especially in OSS. It just worries me that the greater community will think Deno is just another serverless framework, rather than a versatile and awesome tool like Node (but better)
0
Jun 22 '22
[deleted]
6
u/Swingline0 Jun 22 '22
You make a good point. I can definitely vibe with that and I hope it's successful. I really want to see Deno succeed and, along with that, improve the quality of life of my staff.
It's more that I'm scared that they're going to fuck up Deno's momentum by confusing people about what it is and thus inhibit widespread adoption because they went too niche. Like if React was actually just a library of Vercel's, introduced in conjunction with Next or Vercel's hosting. It wouldn't have had the clout or the adoption to bring our community along with it.
As long as the greater community comes along, we can have a similar vibrant ecosystem like what we enjoy for Node and React.
For the record, Vercel is doing amazing work. They're the gold standard of developer experience imo
2
7
3
u/kazzkiq Jun 22 '22
What about performance? Does Deno has any advantages over Node.js in this regard?
5
Jun 22 '22
For any JS/TS beginner out here, Deno is the best way to start. You don't need anything, no package.json, no tsc, no compilation, no setup. All you need is to install Deno (and possibly VS code extension) and you can immediately run TypeScript, and all of the package management is done automatically.
8
3
1
1
1
u/Antifragile_operator Jun 24 '22
Impressing, especially given where the VC market are heading these days!
1
u/ArnUpNorth Jul 14 '22
Remember the « big fork » early in nodejs history with io.js splitting the community ? Few seem to remember but history often repeats iojs merge with node
I code mainly in typescript so this and better sandboxing for security makes deno attractive…. But this move is bad for the JS backend ecosystem. With WASM opening the path for more languages making their way into the browser the last thing our community needs is to split our focus between two rival projects. Let’s hope that just like what happened with io.js we’ll be able to unite our forces and create value instead of reinventing the wheel.
1
1
u/trieu1912 Jun 22 '22
I am still not interested in Deno. on backend, we can use so many languages like golang python and C# java or even rust So i am not sure it can be a good choice to use Deno now
0
5
Jun 21 '22
[removed] — view removed comment
3
u/Swingline0 Jun 22 '22
The comment that says "Love Deno!" has 12 upvotes but you're at -1 wtf
I'm bringing you up to 0, friend
2
63
u/TheNewOP Jun 22 '22
Not prod ready, but I can't wait to see "Required: 5 years exp in Deno" the day it's released.