I'm very intrigued by Deno. I'm prefer to work in Typescript. And if I was starting a brand new project, why wouldn't I consider Deno? Node was a pretty radical idea when it first launched, but it is showing it's age. The promise of it was that you could leverage all of your javascript knowledge from the browser and use it on the server... EXCEPT for all the things that were different. And to me, it seems like those differences have grown over the years. Would I re-write an existing Node server? No... would I write a new project in Deno. I don't know. I'd like to learn more. As I said in the first sentence, I'm very intrigued by it. I think a lot of other people will be as well.
Dammit and I just completed part 2 of your 4 part series on the library app... Big breath.... Well atleast your a good teacher so I look forward to learning deno from ya
u dont need to worry about switching to deno it still js .. just u will learn another ways to run ur code ... just one or two days enough for switching ... one thing thats u need to care about it is suitability of basic libraries and support of server environment for/to deno
ok the migration process and and waiting for the stable full release makes it take a long time to "replace node" hope that deno will have a migration tool and express js would be the first ones to migrate to deno
Well, there is not much to learn. Most things are equal or very similar to the browser, and some Deno specific features can be seen in the docs, such as Deno.write(), Deno.read(), and so on. What would be more interesting is to see some libraries in action, such as serve.ts or oak.ts for running a web application on the backend with deno. Just download it and try it out! deno.land/
Once it really release, great. Especially the centralized dependencies vs requiring a separate node_modules folder for each project. But for now it is unstable... so will wait. Also switching to Typescript once it releases as a stable version.
Yup Deno + Typescript + Rust is the future. It's pretty raw right now though. I'm kinda hoping we get some SASS / postCSS support ASAP. SASS does have a rust crate, but it hasn't be updated in ages.
I barely knew about the new coolest js runtime, but with the simplified summary in this video and the crash course, I'm really gonna take Deno more seriously due to its awesome features, hope to see in the future how to do common node stuff "the Deno way"
This is one of those cases where I’ll learn about but won’t become a proficient user for maybe 3/5 years. Node.js isn’t perfect, but it’s so good, so well supported, and has a massive commmunity behind it. Anyway, I’m wishing deno the best for 5 years from now 🙏🏽
Thank you so much for your amazing video bro! I'm wondering, how long it gonna take before we see something powerful like Express.js (and express generator) for deno.js? What do you think?
I discovered your channel recently. You make some pretty good videos for different topics. :) Have you thought about doing a video on TypeScript? Or maybe a series, to keep them short?
Of course not! Both Node and Deno are very similar, both are runtime environments. Deno is a little bit closer to the browser and nicer to write code in (fetch, ES6 imports, top level await and promise-based APIs), but everything else is very similar, and node is more complete today (electron and NWJS integration, millions of packages in npm, and so on). So don't worry, just learn Node and you'll be alright. If you wish, try learning both! Both are VERY similar, for real.
So does this mean I can now comfortably build websites with Deno now? I've been wanting to learn node but something kept me back. Now deno is here... I think this one makes me wanna dive in
Can permissions be required at the package level? For example, a deno app is given permission to delete files from the file system. But I do not want that permission to apply to every module imported into the application.
I am just thinking... Now a days, js code that mostly run are containerized (which provide isolation) & the js code generally that you run in local for development are kind of vetted by you. generally you wont import a node module without looking at the code or atleast no. of users using it before using it. I see that deno's future in terms of security is promising but for now just security in terms of files is not enough for me (maybe fine tuning the file access would be better). Also, I kind of like the package-lock.json. It gives me the entire blueprint of the app. I have fixed a lot of bugs just by reading & understanding the modules mentioned in package-lock. Just giving my thoughts for now.
That's JavaScript.... Learning forever without stopping.... I like this cycle! I will go on for node while waiting for Deno, Endo, Onde, oneD, and Done.. By that time I won't be able to run much for JS than for just saying goodby dear earth
Must have seen 100+ posts and videos about Deno and if it will replace Node in the last 3 Days... They are trying too hard to push it. It will never replace node.
Node, Deno, everyday a new technology. I will stay on the safe side and wait until Done is released...
Node is 11 years old.
I’m waiting for Oden
hahaha
I saw that!
Good one
deno: just release v1
some HR: you need at least 10yrs experience on it
🤣
lololololol
😂 true
i realize I am pretty randomly asking but does anybody know a good place to watch new tv shows online?
The future is Nedo, Neod, Oden, Oned, Eond, Edno, Endo and finally Done.
😀🤣
Hahaha
There are 4! Different versions of node!
forgot edon?
@@rendoesmath that too
Why not show some examples? That would have improved the video a lot!
then check this video ruclips.net/video/zFf_fcn0cI0/видео.html
The only sure that everyone should know is vanilla js. Will last for ever
You are so right...
I whether use vanilla js
Scripting is used for controlling desktop api .
Sadly you're right lol
well new versions of that get released too
I'm very intrigued by Deno. I'm prefer to work in Typescript. And if I was starting a brand new project, why wouldn't I consider Deno? Node was a pretty radical idea when it first launched, but it is showing it's age. The promise of it was that you could leverage all of your javascript knowledge from the browser and use it on the server... EXCEPT for all the things that were different. And to me, it seems like those differences have grown over the years. Would I re-write an existing Node server? No... would I write a new project in Deno. I don't know. I'd like to learn more. As I said in the first sentence, I'm very intrigued by it. I think a lot of other people will be as well.
I know you are working on a js course right now but I would love it if you got a node course out. Just working around the node ecosystem. 😬
One of the few channels i press like before watching 1 sec of the video. Love you man! Keep up the good work!
Im already having trouble learning javascript atm. Great another lanaguge.
When Deno 2 will start I will start to learn it too.
Kyle: Want me to make a Deno crash co--
Me: YES!!!
Dammit and I just completed part 2 of your 4 part series on the library app... Big breath.... Well atleast your a good teacher so I look forward to learning deno from ya
I would happily watch that Deno crash course
Kyle: the best content - time ratio on yt. thumbs up
Yip ... A crash course in Deno would be great! :)
Great info, thanks
Thanks a lot for Deno information, it´s useful
I am interested in Deno. Please make a video showing especially middlewares and mongodb usage
Thank you for clarifying if Deno will replace NodeJs. I always trust you opinion on things like this. Time to learn NODE!
Learn JavaScript, you can go for anything. Node, deno it doesn't matter
Deno seems interesting. Everyone's making video on it. 🤔
I agree it is interesting. It just released in V1 which is why so many people are talking about it right now.
@@WebDevSimplified I literally started learning NodeJs 2 days ago. And this showed up. 😆
@@PiyushSuthar well , if u know nodejs deno is easy
@@PiyushSuthar Right!!! I was like Damn am I learning the wrong "language/framework"
probably just marketing
Def interested in Deno.
Great videos, a Deno tutorial would be much appreciated!
u dont need to worry about switching to deno it still js .. just u will learn another ways to run ur code
... just one or two days enough for switching ... one thing thats u need to care about it is
suitability of basic libraries and support of server environment for/to deno
Yess Kyle, deno crash course pls
Deno as a series would be nice. Kinda like giving updates on a new truck.
I'd love to see another video about Deno
Please make a video about the basic things about Deno.
ok the migration process and and waiting for the stable full release makes it take a long time to "replace node" hope that deno will have a migration tool and express js would be the first ones to migrate to deno
Yes do a deno crash course
You are good. I like your videos.
I will address the way Kyle presented all the Deno features with pluses and minuses. Great job!
Nicely explained,
Appreciated
Deno if I should switch from node or not?
Please make a crash course on Deno. Can't wait to see that. Thank you.
Well, there is not much to learn. Most things are equal or very similar to the browser, and some Deno specific features can be seen in the docs, such as Deno.write(), Deno.read(), and so on. What would be more interesting is to see some libraries in action, such as serve.ts or oak.ts for running a web application on the backend with deno. Just download it and try it out! deno.land/
Once it really release, great. Especially the centralized dependencies vs requiring a separate node_modules folder for each project. But for now it is unstable... so will wait. Also switching to Typescript once it releases as a stable version.
Interesting idea
Yes, you should make course on deno.
Yup Deno + Typescript + Rust is the future. It's pretty raw right now though. I'm kinda hoping we get some SASS / postCSS support ASAP. SASS does have a rust crate, but it hasn't be updated in ages.
I'm waiting for your crash course on it
I can't wait that will be very blessed
I was waiting to hear your take on Deno this past week. Thanks for the video man!
I barely knew about the new coolest js runtime, but with the simplified summary in this video and the crash course, I'm really gonna take Deno more seriously due to its awesome features, hope to see in the future how to do common node stuff "the Deno way"
This is one of those cases where I’ll learn about but won’t become a proficient user for maybe 3/5 years. Node.js isn’t perfect, but it’s so good, so well supported, and has a massive commmunity behind it. Anyway, I’m wishing deno the best for 5 years from now 🙏🏽
Thank you so much.
Waiting for crash course!!!
Thank you so much for your amazing video bro!
I'm wondering, how long it gonna take before we see something powerful like Express.js (and express generator) for deno.js? What do you think?
I discovered your channel recently. You make some pretty good videos for different topics. :)
Have you thought about doing a video on TypeScript? Or maybe a series, to keep them short?
So, I started with backend development so I dont really need to use deno because the inbuilt browser apis
Yes, we need a crash course on it, pleeeeeeeeeasde
love the world of javascript always coming with new solutions instead of patching everything
Its because Nodejs is used by big guys like Neyflix, Paypal ,eBay, twitter.....if he changed the API he would break them
What about learning server side for the first time? Should I learn node or dino at start?
Great content like the explanation.
We are waiting for your Deno lessons
Even though the video was just talking I liked it!
Deno is written in rust instead of node which is written in c++? How does rust differ from c++?
Should I stop learning node then? I'm really liking node
Of course not! Both Node and Deno are very similar, both are runtime environments. Deno is a little bit closer to the browser and nicer to write code in (fetch, ES6 imports, top level await and promise-based APIs), but everything else is very similar, and node is more complete today (electron and NWJS integration, millions of packages in npm, and so on). So don't worry, just learn Node and you'll be alright. If you wish, try learning both! Both are VERY similar, for real.
Yes need crash course of Deno
I appreciate the rundown. I'll have to look into this a bit more 🧐
no package.json? I actually found it very nice and descriptive about the project.
Thanks,we are waiting for the crash course 🤘
Yes! Deno tutorial, please! And thank you... Cheers!
You should make a video on node js security and how to implement them when making Android applications?
Deno feels like a runtime based on the architecture of Go written in rust
Please make deno full course tutorial. Thanks
I'd love to see a video on how to use Deno. Wow Deno is in my autocorrect lol
yeah, please make a deno tutorial, we want to know how it works !!!
Kyle, is there anything that can be built with node (or deno) that can't be done with vanilla JS?
Can you make a video about free hosting site wich u said in this video
So does this mean I can now comfortably build websites with Deno now? I've been wanting to learn node but something kept me back. Now deno is here... I think this one makes me wanna dive in
bless darah Wouldn’t bother, you’ll put the time into learning only for something to replace this two years down the line.
@@slapmyfunkybass The Js ecosystem is full of new things everyday. I mean, it's like the weather.
Hey Kyle, sounds interesting! Would love a short course on that.
Please make a video on upload file with google cloud storage(or another file hosing services) in node instead of using database....please man.
Now I'm start learning node js, I heard deno, please sir make deno video. I thought it's similar to node :)
Yes pls make a Deno tutorial. Im interested in learning Deno.
Go LANG is also taking place in market largely. What if you compare Go lang and deno because both are new ?
I'm gonna use Deno cause it has the cuter logo 😻
lol agree
I became front-end dev because JS is yellow.
@@CastleShield I highly suggest you people not to look down when you shit !
That's a cool idea . Go for a crash course on it .
yup make a crash course on deno plz 😻
Are you going to make a Deno tutorial? Please do! It will be of great help to your subscribers.
Sounds great, a new alternative to build projects.
Have there been updates since this was posted regarding the security risks of Node?
What are the best ways to mitigate them?
Can permissions be required at the package level? For example, a deno app is given permission to delete files from the file system. But I do not want that permission to apply to every module imported into the application.
i want to know if either node or deno can scan with (Deep Content Disarm and Reconstruction) that before storing it to the server
Also has web workers. Meaning you can run threads.
I am just thinking... Now a days, js code that mostly run are containerized (which provide isolation) & the js code generally that you run in local for development are kind of vetted by you. generally you wont import a node module without looking at the code or atleast no. of users using it before using it. I see that deno's future in terms of security is promising but for now just security in terms of files is not enough for me (maybe fine tuning the file access would be better).
Also, I kind of like the package-lock.json. It gives me the entire blueprint of the app. I have fixed a lot of bugs just by reading & understanding the modules mentioned in package-lock.
Just giving my thoughts for now.
Top level await and native fetch is pretty neat though.
@@softwarelivre2389 you can do that in nodejs either
@@aeonthread7970 top level await yes, but under a flag. But no native fetch from what I recall.
I was wonder this exact question! As a new learning programmer I always worry im learning the wrong "language/framework"
Deno tutorial would be great, looking forward to it
Interested.
When deno 2 comes out I would like to see a course.
Please do the crash course!!!
Very interesting, I'd love to see a walk-through of it
Node, Deno, Oden, Endo or whatever they will create in the future will not make Apache go away
This is like what happen in PHP over JavaScript. Learn DENO but don't forget NODE.
That's JavaScript.... Learning forever without stopping.... I like this cycle! I will go on for node while waiting for Deno, Endo, Onde, oneD, and Done.. By that time I won't be able to run much for JS than for just saying goodby dear earth
I just blink eyes and a new framework of JavaScript comes
So time to learn the MERD stack?
Must have seen 100+ posts and videos about Deno and if it will replace Node in the last 3 Days... They are trying too hard to push it. It will never replace node.
Hi Kyle, can you do an update Deno?
I am waiting for done
No harm to build something with deno and truly understand its characteristics.
Could we consider it as Deno(de)??
I’d love to see a video on Deno! Seems really interesting at the very least.