This is a good video! 👍 I just realized after using Deno for many months and creating APIs, I just noticed you really do not need a flag to "allow all to yes", and it makes sense because when you launch or publish your Web App.. You really not need to access filesystem to write because you just let the API do its process to do the CRUD into a database. This does makes sense and expect it to be a READ-ONLY... This prevents API access your critical filesystem... There is a lot of NPM that has major access to filesystem and there is no certain control to block those interfering the filesystem and there are many ways to bypass it that is the reason why NodeJS always require to keep on updating to latest version for security vulnerabilities... Security should be the first priority! 👍
Thanks a lot for the fantastic explanation! I've watched the entire thing and I'm really into Deno 2.0. I'll definitely be rewatching it and following you to enhance my understanding. Thank you so much!
I've already try it (by the way with HonoAdapter instead of Express)... it works! (Im only waiting when the upgrade deno version on their deno deploy to start hosting my nestjs app here)
@@NikKita-f8i great I want to see Hono is interesting... I want to get star in backend and I am trying to avoid Node lol but I am digging deep, I'd always holpind Deno bring something modern like AstroJS did /gt version 2 seems great, Bun is nice to use with packet manager lol I am using instead PNPM in all astro projects right now :). Bun seems nice but I have seen some bugs in simple installations with Astro with me trying to build with AHA Stack with Bun instead Node, But Astro was built in Node, I'd want an Astro version built with Deno \o/ it would be all kind of project simple medium and enterprise level easy to acomplish by Layers ... When you make some discoveries I will be happy to see about your experiences all right? I wish you good luck I'll back here too :)
It's incompatibility with Node was it's biggest mistake and what left the window open for yet another runtime we could actually use without setup I guess it still was kinda necessary to reach the point we are now I'm pretty happy of it's current state and starting to use it, although at times it was still a bit confusing coming from Node
Deno with npm:nextjs install requires NPM to be installed! Ugh, what a bug! And the custom `page.tsx` example in the final demo that hits `/api/hello` needs `"use client";` statement at the top for nextjs.
Not much for now because Expo runs on Babel and Metro, which are entirely different technologies. If you want something close to Deno on mobile devices, checkout One. It's a (you guessed it) new React framework that leverages 'vxrn' (vite x react native) to build cross platform react apps running on vite. One is still in Beta but I've been playing with it and got Deno 2 to work with it!
🦸 Become A VS Code SuperHero Today: vsCodeHero.com
I went further and forgot Deno even existed :)
😂😂😂
and we also went further and forgot about you even commented:)
@@NikKita-f8i lol, it was just a joke, Deno 2.0 looks really interesting!
@@codernerd7076 Im sorry)
This is a good video! 👍 I just realized after using Deno for many months and creating APIs, I just noticed you really do not need a flag to "allow all to yes", and it makes sense because when you launch or publish your Web App.. You really not need to access filesystem to write because you just let the API do its process to do the CRUD into a database. This does makes sense and expect it to be a READ-ONLY... This prevents API access your critical filesystem...
There is a lot of NPM that has major access to filesystem and there is no certain control to block those interfering the filesystem and there are many ways to bypass it that is the reason why NodeJS always require to keep on updating to latest version for security vulnerabilities... Security should be the first priority! 👍
Thanks a lot for the fantastic explanation! I've watched the entire thing and I'm really into Deno 2.0. I'll definitely be rewatching it and following you to enhance my understanding. Thank you so much!
Thanks! Glad it helped 🙌
Deno has it all.
Thanks Jesse!
Thanks for watching!
handleRequest method at t 19:00 must be async to work with Promise return type.
I stayed up late to watch this. So it must be done well for me to lose sleep over !! Thanks
Love this, thanks for the effort Jesse ❤
Thanks!
Great video! Thanks for sharing your experience with Deno, i need to give it a try
Deno 2.0 ❤
Can you use Deno for micro services? I am trying to decide between Java or Deno for a POS app using micro service. What would you recommend?
Yes! But I’m not a java dev so I would choose Deno 😅
@@codeSTACKr😅I think I will use Deno ! You convinced me!
Do you know how to deno run nestjs?
I've already try it (by the way with HonoAdapter instead of Express)... it works! (Im only waiting when the upgrade deno version on their deno deploy to start hosting my nestjs app here)
@@NikKita-f8i great I want to see Hono is interesting... I want to get star in backend and I am trying to avoid Node lol but I am digging deep, I'd always holpind Deno bring something modern like AstroJS did /gt version 2 seems great, Bun is nice to use with packet manager lol I am using instead PNPM in all astro projects right now :). Bun seems nice but I have seen some bugs in simple installations with Astro with me trying to build with AHA Stack with Bun instead Node, But Astro was built in Node, I'd want an Astro version built with Deno \o/ it would be all kind of project simple medium and enterprise level easy to acomplish by Layers ... When you make some discoveries I will be happy to see about your experiences all right? I wish you good luck I'll back here too :)
It's incompatibility with Node was it's biggest mistake and what left the window open for yet another runtime we could actually use without setup
I guess it still was kinda necessary to reach the point we are now
I'm pretty happy of it's current state and starting to use it, although at times it was still a bit confusing coming from Node
@@ivlis.w8630agreed. thanks for the feedback.
How does bun compare to deno 2
Playright it's work?
Yes!
Great!
Glad you liked it!
Did i have to learn node.js to understand well deno ?
Thanks really cool
You're welcome!
Deno with npm:nextjs install requires NPM to be installed! Ugh, what a bug!
And the custom `page.tsx` example in the final demo that hits `/api/hello` needs `"use client";` statement at the top for nextjs.
Because the issue here is not with Deno but with nextjs being a nodejs project, maybe at some point we will have a fully Deno First react framework
I wonder that deno how can effect react native/expo stack, too
Not much for now because Expo runs on Babel and Metro, which are entirely different technologies. If you want something close to Deno on mobile devices, checkout One. It's a (you guessed it) new React framework that leverages 'vxrn' (vite x react native) to build cross platform react apps running on vite.
One is still in Beta but I've been playing with it and got Deno 2 to work with it!
New subscriber here 😊
Thank you!
But it even can't import local npm package. Wasted my time.
You absolutely can. You can use any existing node app with a node_modules folder and it will now work with Deno.
@@codeSTACKr Nope, it has no ability to work with local npm packages.
deno is cool, but i found bun much better.
'Game Changer', even c is not game changer compare to assembly, please stop this crap. I'm interested how close to slownest is to bun or go.