I totally agree. When building a small MVP or just testing something out, using Deno or Bun is really convenient because you don’t have to worry about setting up TypeScript, a linter, or a test runner. However, for larger projects, the compatibility issues become overwhelming. Additionally, when working in a team, every new member usually has to learn the new APIs.
I'd think it's at least worth considering having to do less imports (larger standard library, node is religious about not adding to their standard library), the built in things that you mentioned rather than being part of the build system, added default security features, and more things to, as qualities that would balance that out.
@@i3looi2 Vanilla JS isn't hard. Its poop. A good standard library is a feature of any well respected language. Not that I expect JS soydevs to understand that.
Thanks for the Deno content and for mentioning Fresh! I would absolutely love a Fresh tutorial from you that featured how we can incorporate some of these great new Deno 2.0 features and also went into a bit about how Fresh uses Preact for a lot of it's State/Component stuff.
I've used Deno for several years for almost all of my personal projects and it's pretty fire. I've been pretty anti dependency so the npm compatibility issues haven't been a big deal, but now the npm support is great. I've liked it a lot.
@@Mr.BinarySniper being using it mainly for mostly a year now, it is not just a hype, it is much faster and efficient than node and the compatibility issues decreased significantly.
bun will always be a fork of node/deno, it's redoing the underlying implementation in zig which may/may not be the direction the community will opt for/contribute to as node is a javascript ecosystem, bun will always behind as the first purpose is optimization
I have used Deno pretty much from it's first release and I love it. Only reason I've used Node is for projects which used front-end frameworks which weren't compatible, so this is a huge win as far as I'm concerned, and I will probably start all of my new projects on Deno.
Love this channel and Kyle is amazing, but the head shake/wobble is so distracting sometimes, I just zone out and watch his head moving and then I have to rewind the video to catch the parts I missed.
Thanks, Kyle! As a downside of current state of Deno you should have probably mentioned their stubborn decision to have imports contain ts extension. Last time I checked, there were a decent amount of people requesting the status of making file extensions in import statements optional. This lands as a con to me, and pretty heavily, too, since it essentially prevents you from copying your existing code as is, you will have to edit each file to set up file extensions for local imports. This anti-feature has actually killed my starting-to-grow enthusiasm.
Deno is being used in prod, e.g Netlify,Ssupabase, Slack. Apparently, it's really great as a platform tool for serverless. Also, because of its security features, it can be a good choice for prod even if you use node during development.
I think it would be cool to learn how to move to deno2 while keeping the source code compatible with node so if you meet a deal breaker you can eject back to node. I love the idea of deno2 and starint a new project totally makes sense to start with deno but it's important to do it in a way where if turns out my favourite node.js library doesn't work with it i can easily eject back and run the project using node. What i'm trying to say is would be great to have a guide on how to develop backward compatible source code with deno so we can start migrating and creating new projects with deno without fearing of hitting a dead end.
I was excited so I tried it and -- it left .deno droppings throughout my node_modules and screwed up file links which it doesn't (yet?) support. I'll be more cautious when I try a test run. I really want to like deno but ...
Its so nice how deno & bun are pushing things forward. I kinda wished node would just take the bullet & die so the greater js ecosystem could move on to a better standard, but I am impressed how much better node 22 is coming along vs where node 16 was at not so long ago. I think bun is easier just start using (till it breaks) but deno 2 looks like it could really bridge the gap.
Might have planned this video release timing just a bit prematurely. Current target (but not commitment based on discussions in the Deno Discord) is next Friday.
Deno does not aim to be a Node replacement, it mainly just want to provide native TS support for a web application run time. But the ecosystem is just too involved around node, and now with node aiming too provide TS support natively too, it's be really hard on the Deno team if people don't want to develop library in Deno
I hope it does replace it. I think Deno is the future. I have been using it for about 1 1/2 years, and it is fantastic. I use it as much as possible unless I can't avoid it.
Deno unlike Node is bound to go corpo eventually. The only positive light I see from it is that it might push node to get better. Maybe steal some good features 😅
in the real world most companies don't change tech too often so no, with the original node runtime adding TS support i don't see a big reason to switch anyway
node is slower then bun for example and requires a lot of additional shit bundled, probably the best option would have been t okill the node and concentrate on developing bun/deno
This is a tradition. As soon as some freak stuff like bun or deno rolls out, every single programming UA-camr posts 10-15 min video with clickbait thumbnail "Deno / Bun: node js killer?", "Bun or Deno or whatever kills Node js!". Who cares?
UA-camrs blabbing about replacing or killing node is getting kinda annoying. The creator of node never intended to replace anything or kill anything, of all people he knows node can probably never be replaced. He just moved on and started a new and hopefully a better project, that's software development. I don't get this kind of content...
The idiosyncrasy of saying that one solution kills another is mindbogglingly strange to me. Nothing is killed in software land. It will always coexist with similar solutions.
another thing in JS world .... everybody .....run run towards it ...until some one gets up tomorrow and announces hey I have created another lib/framework
No, it won't. Too many applications based on Node and too much money and time have been invested in those projects. Same as the PHP based stuffs. For the next N years they will stay.
The problem with bun and deno is that if you want something better than node for back end stuff and you have a choice….you just use something that’s not js. It’s the same reason none of these front end ui frameworks have replaced react, even though each one is technically better . It’s not going to be a slightly better js rendering spa framework that eventually replaces it, it’s going to be a different paradigm entirely
I agree, I personally use Go now as default for my backend. However, let's not ignore the big advantage that is having frontend and backend using the same language
Bun will rule next year's and node will be like angular and will shade away. So node has no future, so need high level framework on top of bun. So learning pure node is waste maintenance of poorly documented nodejs project is total waste
@@boot-strapper Ah yes I remember exactly those benchmarks from last year by whoever it was in which they actually showed that Deno is faster. We keep winning 🦕
are you paid by deno my friend? deno is hyper commercial, they spend more money in PR and I am pretty sure in the future more and more commercial shit will be implemented like every "half-free" software does. at the end the "comfort" features are laughable or shouldn't even a part of a runtime environment. and in the benchmark part Bun is even faster and has even more height-performance stuff like a build-in sqllite db and more... and btw. things like fetch are native js funktions since years.
Not replace, but an absolute great competitor pushing JS forwards. DX is really nice
I totally agree. When building a small MVP or just testing something out, using Deno or Bun is really convenient because you don’t have to worry about setting up TypeScript, a linter, or a test runner. However, for larger projects, the compatibility issues become overwhelming. Additionally, when working in a team, every new member usually has to learn the new APIs.
I'd think it's at least worth considering having to do less imports (larger standard library, node is religious about not adding to their standard library), the built in things that you mentioned rather than being part of the build system, added default security features, and more things to, as qualities that would balance that out.
the reason run run js front or bank . its easy one month one framework and maintain ouch horrible
my teammembers are all named "ChatGPT" so if ChatGPT knows the API, i'm sold
the standard library is a killer feature.
no is not. maybe if u were the kind of dev who still adds Lodash to every project only to use 2-3 functions cause Vanilla JS too hard.
@@i3looi2 bad take :/
@@i3looi2 Vanilla JS isn't hard. Its poop. A good standard library is a feature of any well respected language. Not that I expect JS soydevs to understand that.
No one likes setting up jest or vitest@@i3looi2
@@i3looi2 agreed. lodash is trash bloat lol.
Thanks for the Deno content and for mentioning Fresh! I would absolutely love a Fresh tutorial from you that featured how we can incorporate some of these great new Deno 2.0 features and also went into a bit about how Fresh uses Preact for a lot of it's State/Component stuff.
I've used Deno for several years for almost all of my personal projects and it's pretty fire. I've been pretty anti dependency so the npm compatibility issues haven't been a big deal, but now the npm support is great. I've liked it a lot.
The other question: Will Bun replace Deno 2.0 that will replace Node.js?
Nope. Bun is a hype. you will understand that soon.
@@Mr.BinarySniper Thanks, it was just a spin on the video title
@@Mr.BinarySniper being using it mainly for mostly a year now, it is not just a hype, it is much faster and efficient than node and the compatibility issues decreased significantly.
bun will always be a fork of node/deno, it's redoing the underlying implementation in zig
which may/may not be the direction the community will opt for/contribute to
as node is a javascript ecosystem, bun will always behind as the first purpose is optimization
and WinterJS will replace all 🤔
Deno 2.0 is awesome. The fact that it is just one single executable is mind boggling!
I have used Deno pretty much from it's first release and I love it. Only reason I've used Node is for projects which used front-end frameworks which weren't compatible, so this is a huge win as far as I'm concerned, and I will probably start all of my new projects on Deno.
What documentation you followed??
If Deno 3.0 adds head wobbling feature, they will not only kill Node.js but also your channel too!
The level of roast... 💀
Love this channel and Kyle is amazing, but the head shake/wobble is so distracting sometimes, I just zone out and watch his head moving and then I have to rewind the video to catch the parts I missed.
@artemonstrick F*** Y**. I am not sure how, but I never noticed until this comment. Now I will never be able to unsee.
Does the content important for you anyway or just his head shaking? Stop this nonsense hate and go to other channel
Bruh why he catching strays like this 💀
Thanks, Kyle! As a downside of current state of Deno you should have probably mentioned their stubborn decision to have imports contain ts extension. Last time I checked, there were a decent amount of people requesting the status of making file extensions in import statements optional. This lands as a con to me, and pretty heavily, too, since it essentially prevents you from copying your existing code as is, you will have to edit each file to set up file extensions for local imports. This anti-feature has actually killed my starting-to-grow enthusiasm.
Deno is being used in prod, e.g Netlify,Ssupabase, Slack. Apparently, it's really great as a platform tool for serverless. Also, because of its security features, it can be a good choice for prod even if you use node during development.
Yeah, I was a bit skeptical of Deno Deploy, but having tried it, it's actually quite nice.
I think it would be cool to learn how to move to deno2 while keeping the source code compatible with node so if you meet a deal breaker you can eject back to node.
I love the idea of deno2 and starint a new project totally makes sense to start with deno but it's important to do it in a way where if turns out my favourite node.js library doesn't work with it i can easily eject back and run the project using node.
What i'm trying to say is would be great to have a guide on how to develop backward compatible source code with deno so we can start migrating and creating new projects with deno without fearing of hitting a dead end.
and also can make executables, i can see being useful to just make home servers and be able to share that executable to run those API calls
you don't need deno to make executables.
@@emanuelec2704 oh you dont? whats the node.js command to do so? never heard of it
Nice Content dude.keep doing it . don't think about one's talk bad( i mean trash ) about your channel. U r channel is the best 😎 🐐.
Thanks for diving deep!
Reading right from Deno 2 media doc and not realizing that Deno 2 is out next week :)
I was excited so I tried it and -- it left .deno droppings throughout my node_modules and screwed up file links which it doesn't (yet?) support. I'll be more cautious when I try a test run. I really want to like deno but ...
very hyped for more stdlib stuff
Deno imports make up 99% of frustration of working with it. I tried to get into it without expectations, but still was disappointed
With version 2?
Its so nice how deno & bun are pushing things forward. I kinda wished node would just take the bullet & die so the greater js ecosystem could move on to a better standard, but I am impressed how much better node 22 is coming along vs where node 16 was at not so long ago.
I think bun is easier just start using (till it breaks) but deno 2 looks like it could really bridge the gap.
JSR looks like a real upgrade, but it's available for NodeJS too, isn't it?
i need something to run typescript from go. is there an api/sdk to embed deno ?
Many already came, many will come but node js is always the goat for
I will begin using Deno 2 once Svelkit is supported, though I’m aware that Svelte is already supported.
Might have planned this video release timing just a bit prematurely. Current target (but not commitment based on discussions in the Deno Discord) is next Friday.
Deno does not aim to be a Node replacement, it mainly just want to provide native TS support for a web application run time. But the ecosystem is just too involved around node, and now with node aiming too provide TS support natively too, it's be really hard on the Deno team if people don't want to develop library in Deno
I hope it does replace it. I think Deno is the future. I have been using it for about 1 1/2 years, and it is fantastic. I use it as much as possible unless I can't avoid it.
Hey Kyle, Can you please create video on fastify v5. I would love to watch it.
Please give us some info about bun.js and should we use bun or deno or node
Deno unlike Node is bound to go corpo eventually. The only positive light I see from it is that it might push node to get better. Maybe steal some good features 😅
Hi, could you share this summary document? Thank you.
can we get a performance comparison against nodejs and bun?
so instead 1 we have 3 compatible libs? node deno and bun?
Wszystko co nowe jest świetne, cudowne i jest lekarstwem na problemy tego świata.
Whats with the head shake??
You should talk about Bun.js
How does it compare to Bun?
ms sql bağlantısı hakkında bilgisi olan var mı?
Ben Deno ile yapamadım. O yüzden ya nodejs ya da php kullanıyorum.
Seems good but I dont know... I dont wanna deal with compatibility issues.
How many JS framework and runtime do you need to learn ? Yes.
What is with BUN? 😊
(Honestly - Deno and Bun are more experemental, for production Node is most used. Mbe unfortinately. Cos "safety")
ua-cam.com/video/dPO4v5q9ULU/v-deo.htmlsi=pPXRmTqolhkBPMnx
oh fuck here we go again
I;m just waiting on NODENO to replace Deno. That way it comes full circle
Fun fact: if you translate "nodeno" to italian, and back to english you get "little knot"
😅
i've used bun in prod and performance is good actually
bun js support al npm libraries and 3 time faster than deno but it only support linux and mac it has built in support for typescript and all features
Man, with this I think I will actually finish my dream project. Sorry about this Kyle. Looks like you're going out of business.
Clerk has had a lot of problems in Next.js 13 too
Every time i learn development new technology comes out and theier recruit eligible terms changes
2045 ==> "Deno 5.0 the Node.js killer!"
When will you ever make NestJS content?
I don't see no deno 2.0 release anywhere being released 🤔
Will typescript replace js?
They need to start being supported by NestJS before I consider them.
in the real world most companies don't change tech too often so no, with the original node runtime adding TS support i don't see a big reason to switch anyway
node is slower then bun for example and requires a lot of additional shit bundled, probably the best option would have been t okill the node and concentrate on developing bun/deno
but didnt bun had already been doing it but faster ?
have you seen Bunjs? It can also bundle and even compile to binary file.
waw, they just killed several known libraries. the future is going nuts. gotta update my stack!
Will Deno support Electron.js?
This is a tradition. As soon as some freak stuff like bun or deno rolls out, every single programming UA-camr posts 10-15 min video with clickbait thumbnail "Deno / Bun: node js killer?", "Bun or Deno or whatever kills Node js!". Who cares?
Me :3
You’ve successfully escaped the matrix 🎉
As well as every vscode killer/ chatgpt killer out there
😂 You. That's why you commented.
What can deno do that node can’t?
If you come from Rust and the whole toolchain is way more unified, its a pleasing. The same in go. I also like the native single binary option. : )
It can sell you denos hosting.
@@D9ID9I Yeah I’ve heard on honeypot that they wanted to commercialize this time.
@@Skylla54 Appreciate the input
Can you share us the google docs template?
But Kyleeeee do you HAVE A "BUN" N THE OVEN XD
Arc looks clean 🌟
UA-camrs blabbing about replacing or killing node is getting kinda annoying. The creator of node never intended to replace anything or kill anything, of all people he knows node can probably never be replaced. He just moved on and started a new and hopefully a better project, that's software development. I don't get this kind of content...
It's called clickbait.
The idiosyncrasy of saying that one solution kills another is mindbogglingly strange to me. Nothing is killed in software land. It will always coexist with similar solutions.
not using Notion or obsidian? google docs ftw lol
I like deno
could you use dark mode more. My eyes are burning 😵😵😵
Even the website does not open
Who uses deno in prod?
Which is better to learn in 2024
Node js, Golang or java
Golang is literally goated
Node JS is not a language.... I think they're all good, still diffused languages. It's up to you to decide
Go with Java.. it will make you appreciate Typescript more.
@@ColinRichardson 😆
Java or C# if you want work
deno again?
Sorry but the real problem is that nodejs has more time so we all feel more confident. More time means more updstes and bug fixes.
Can u make app that counts how many times you shake your head in each video?
Using npm is 2024 is very hard to justify.
Bun js ??
Bun say "write once, cache anywhere". 😂
Oh boy, here we go again. Of course v2 will kill node.js, then v3, v4, etc😂
Bro, why don't just they replace the javascript? 🤐
Strosin Burgs
And what ever happened to BUN?
Please don't shake your head. I'm getting distracted.
another thing in JS world .... everybody .....run run towards it ...until some one gets up tomorrow and announces hey I have created another lib/framework
Did you notice this?
no'de 🔄 de'no
....... .. Congrats, you just realised the 6 year old joke.....
The creator of Node is the creator of Deno. He named it that way on purpose.
Me who just start learn node🗿
Wtf why lodash on 2024
Why not bun though?
Segfaults 😂
No, it won't. Too many applications based on Node and too much money and time have been invested in those projects. Same as the PHP based stuffs. For the next N years they will stay.
If Deno hasn't taken off all this time, I doubt it will ever happen. I'd rather bet on Bun
Betting on segfaults? 😂
@@RustIsWinning I never had one since months, Bun is getting there!
Yeah and Bun is just faster
The problem with bun and deno is that if you want something better than node for back end stuff and you have a choice….you just use something that’s not js.
It’s the same reason none of these front end ui frameworks have replaced react, even though each one is technically better . It’s not going to be a slightly better js rendering spa framework that eventually replaces it, it’s going to be a different paradigm entirely
I agree, I personally use Go now as default for my backend. However, let's not ignore the big advantage that is having frontend and backend using the same language
Bun will rule next year's and node will be like angular and will shade away. So node has no future, so need high level framework on top of bun. So learning pure node is waste maintenance of poorly documented nodejs project is total waste
I believe node will still be the king
bun is still better
Never was. Deno is winning 🦕
@@RustIsWinning deno is slow
@@boot-strapper Source?
@@RustIsWinning any benchmark from the last year
@@boot-strapper Ah yes I remember exactly those benchmarks from last year by whoever it was in which they actually showed that Deno is faster. We keep winning 🦕
Go or Kotlin for the win
npm run bun --deno 😅
☝☝☝☝
are you paid by deno my friend? deno is hyper commercial, they spend more money in PR and I am pretty sure in the future more and more commercial shit will be implemented like every "half-free" software does.
at the end the "comfort" features are laughable or shouldn't even a part of a runtime environment. and in the benchmark part Bun is even faster and has even more height-performance stuff like a build-in sqllite db and more...
and btw. things like fetch are native js funktions since years.
Enterprise of bugs
can wait deno 2.0 killer called "done".
why are you shaking your head all the time?
It is so distracting I only watch 1/20 uploads because I know it will annoy the hell out of me.
lmao it's something i noticed early about him. it's funnier when you play at 2x speed. but he's a great tutor so just ignore it
{2024-09-08}