> be me > get new "web standards" typescript runtime > try to reference "AudioContext" because web standards > throw computer through window > go outside to actually touch grass > feelsgoodman
Integrating Node APIs and npm packages into Deno could introduce some complexity and potentially affect performance due to compatibility layers and additional overhead. No?
Adding the compatibility layer for Node does introduce complexity, but not any overhead. We're committed to performance and keep an eye on all of our releases, and so far performance has improved with all of these additions.
@@Cyber_Lanka I haven't experienced any problems. But I would like to know of any, if you could share something specific, it would be helpful, especially if it's about a database driver.
One thing I cannot understand, why do we need to use ‘DENO_JOBS=4 deno serve --parallel main.ts’ instead of ‘deno serve --parallel=4 main.ts’. It’s so confusing.
Maybe the the deno execution context is initiated before cli params are parsed inside V8 so it needs to be an env variable ie mulitthread is just a wrapper
You can install dev dependencies into node_modules with `deno install`. But if you want to install deps to `devDependencies` into your package.json, we're currently working on it!
Great work! I'm soooo looking forward to V2!!! One thing I really wish for V2: Nicer peer dependency management, writing React packages, and running React apps, alls written in deno! I've been really struggling with that, and all examples I found were either not working, very slow, or just felt very hacky. Being able to write frontend packages and test them in a monorepo, without having to do some hacky compilation step using dnt, that would be amazing.
Deno operates with a single TS dialect, unlike Bun. That leads to many benefits, e.g. TS-native library authoring. So much mess with d.ts and module formats, etc. become a non-issue. But I'm currently on Bun because it "just works" and because it's written in Zig (I have a Rust derangement syndrome). I might give Deno another chance later in the game, though.
Deno Deploy, All-In-One out of the box: no build TypeScript, security, test, parallel server on all cores, offline capable package manager like Yarn and PNPM, and so much more
So instead of improving NodeJS, we build another runtime which doesn't support installing packages as devDependencies yet and many npm packages. Great!
@@mukhlimkurowo yes I was just thinking about it. It takes a lot of time and it's so risky. So yeah deno's existence makes sense after thinking about it.
@@RustIsWinning Werent segfaults an issue like few years ago I believe then patched it pretty quickly? I had been using it for a nearly a year now and I cant really find any bad thing that I can say. Plus its faster then deno cuz its written in zig.
@WydionWytcher-o9 well, I tried Deno, but eventually switched from Node to Bun... Benefits are clear: it's NPM compatible, it's super fast, it works. If there's almost no cost of migrating from NodeJS and many benefits - why not to migrate? Deno's huge mistake was to add NPM/Node compatibility such late in the game. I'm going to be with Bun midterm, and switch to another language (maybe Mojo) longterm.
all my homies love deno
Smiling through it all! Can’t believe this my life
Sup homie
i love bun
I love deno too even though I don't know what it is 😂
See you on deploy with JSR incompatibilities, still love and i guess things will fit together some day
Deno: Node and NPM are a mess, this is why we made this
Also Deno: We support Node APIs and NPM packages.
because they are actually not a mess all Ryan Dahl needed was touching grass and take a break instead of creating Deno.
@@ivan.jeremic but deno is better in some aspect compared to Node. And because of Deno node is also making quite a good progress.
@@shirshak6738 because of bun*
> be me
> get new "web standards" typescript runtime
> try to reference "AudioContext" because web standards
> throw computer through window
> go outside to actually touch grass
> feelsgoodman
the nature has built-in hardware accelerated audio 🤯💀
Love the style of the presentation. Makes the information easy to digest 💡
Very nice! Congrats Deno 🎉
Exited for deno 2, hope the lsp works well with de node compatibility
Integrating Node APIs and npm packages into Deno could introduce some complexity and potentially affect performance due to compatibility layers and additional overhead. No?
Adding the compatibility layer for Node does introduce complexity, but not any overhead. We're committed to performance and keep an eye on all of our releases, and so far performance has improved with all of these additions.
Great to hear this @@deno_land
Loving Deno!
I love what you've created with JavaScript. :)
Finally it know how large node community is, and “compatibility just win”🎉
This is all exciting. But without good community support and basic things such as good database drivers there's not much you can prototype or build
But NPM drivers are supported :)
@@jacsamg not completely without issues, no. Because node compatibility layer is not perfect
@@Cyber_Lanka I haven't experienced any problems. But I would like to know of any, if you could share something specific, it would be helpful, especially if it's about a database driver.
Thanks to bun we now have some node compatibility in deno 😅
That is why we can continue using node:)
Why is the voice so familiar?
I think it's the same guy from the channel called Awesome
@@xLastxTemplarx I knew I’ve heard his voice before lol
also using the same meme that was used by Awesome
@@xLastxTemplarx ya ya ya.. i remember now 😂
Awesome. Keep up the good work 👍
Anyone knows which tool he use to present? It's so neat and clean
Excellent release thank you!
Looking forward to Fresh 2 as well
God I love Deno!! ❤️
One thing I cannot understand, why do we need to use ‘DENO_JOBS=4 deno serve --parallel main.ts’ instead of ‘deno serve --parallel=4 main.ts’. It’s so confusing.
environment variable?
Maybe the the deno execution context is initiated before cli params are parsed inside V8 so it needs to be an env variable ie mulitthread is just a wrapper
Вот это добрейшее утро;)
Speed comparison with node and bun?
What's the right way to install dev dependency in deno? I tried it but can't seem to get it. It's more trivial to do in bun
You can install dev dependencies into node_modules with `deno install`. But if you want to install deps to `devDependencies` into your package.json, we're currently working on it!
Let's go deno
Love your deno_fmt. Thank you!
Awesome news
Great work! I'm soooo looking forward to V2!!!
One thing I really wish for V2: Nicer peer dependency management, writing React packages, and running React apps, alls written in deno!
I've been really struggling with that, and all examples I found were either not working, very slow, or just felt very hacky. Being able to write frontend packages and test them in a monorepo, without having to do some hacky compilation step using dnt, that would be amazing.
Thanks for sharing your thoughts. The team is aware of your use case!
Would you mind sharing more information about your mono repo that requires using dnt? We can probably suggest some ideas on simplifying that setup.
deno tryin hard to beat node 🤣🤣🤣
I guess they say "trying" to mean "succeeding" where you're from
@@UliTroyo nah man u deno fanboy look what they did just get a fraction of node's power
@@sad_man_no_talentwhat is that power that you are talking about? Ohh you mean the power of being outdated...
@@RustIsWinning another fanboy u need to find it yourself otherwise u won't learn
@WydionWytcher-o9 I commented 3 weeks ago and looks like u got here after seeing deno 2.0 huh where have u been before that?
time to replace node
hell the fuck yes!
Some can this is Awesome 😊
Thats actually huge you support gcloud stuff now bun has never really hot these packages to work
Amazing!!!
Genuine Question, How is this better than Bun?
Deno operates with a single TS dialect, unlike Bun. That leads to many benefits, e.g. TS-native library authoring. So much mess with d.ts and module formats, etc. become a non-issue. But I'm currently on Bun because it "just works" and because it's written in Zig (I have a Rust derangement syndrome).
I might give Deno another chance later in the game, though.
What’s PQLite? Is this SQLite typo?
No, PGLite is a thing now
POLite
> much awaited
async joke :3
I love deno but the lsp in neovim could do better
i love BunJS 🎉
Well I learned my lesson, guess I won't click on any Deno 2 stuff in the future
Thumbnail literally says "Deno 2 coming soon" not "Out now"
can it run webpack?
And? why should i choose this over node runtime?
because it's deno and logo is better than then node
Deno Deploy, All-In-One out of the box: no build TypeScript, security, test, parallel server on all cores, offline capable package manager like Yarn and PNPM, and so much more
@@sudodesire What you say is more convincing.
It has a standard library
Because Rust.
is it true that you're slower than node and bun?
I believe Deno is not slower than Node.js in general, but it may be slower with something written for Node.js using Node-specific APIs
Depending on the benchmark, Deno is faster than both Node and Bun. Give it a shot and let us know 😎
what about Bun? 😂
Can Deno beat Python in performance?
Everything beats Python in performance...
The _V8 JavaScript Engine,_ which Deno leverages, has always been much faster than Python. Much faster.
So instead of improving NodeJS, we build another runtime which doesn't support installing packages as devDependencies yet and many npm packages. Great!
node cant be improved in a significant way
@@mukhlimkurowo yes I was just thinking about it. It takes a lot of time and it's so risky. So yeah deno's existence makes sense after thinking about it.
Starting fresh allows for new architectural decisions that may not be feasible in Node without breaking changes.
@@RR-bz8bi yeah yeah I replied to the other guy about this.
wtf is this clickbait title, you didn't even talk about Deno 2.0 are you serious
who uses deno anyways 👀
three dots > don't recommend this sh1t
@@iriteshme
The updates are to prepare for version 2
2:40
Isnt bun better tho?
Better in segfaults 😂
@@RustIsWinning Werent segfaults an issue like few years ago I believe then patched it pretty quickly? I had been using it for a nearly a year now and I cant really find any bad thing that I can say. Plus its faster then deno cuz its written in zig.
@@cromrin yep they fixed all crashes and accidentally left open more than 400 issues + Zig is clearly faster in segfaulting lmao
Bun has a whole different vibe than Deno. Deno has been extremely solid & stable in everything I've used it for.
@WydionWytcher-o9 I would suggest you to learn a system programming language. Maybe one day you will understand how things work...
what is this for actually? I don't see point of using it if I have already javascript in my browse and it runs js scripts well
To run web servers and backend applications, handle databases, and process files directly from JavaScript or TypeScript.
Your monotonous voice and intonation are worse than those generated by AI
The problem with deno is typescript, fuck that shit
You don't need to use TS in Deno.
You hate those who write garbage typescript and force you to conform to their garbage code, not typescript itself.
Is Python better? What high-level programming language do you propose then?
People who hates TS have seriously a mental illness because they love to work more instead of making their life easier with types
The style of these presentations is a reason why Bun has outpaced Deno. Less memes, more information please.
That's your opinion 👎🏻
needless to say we don't share it 🥱
@WydionWytcher-o9 well, I tried Deno, but eventually switched from Node to Bun... Benefits are clear: it's NPM compatible, it's super fast, it works. If there's almost no cost of migrating from NodeJS and many benefits - why not to migrate? Deno's huge mistake was to add NPM/Node compatibility such late in the game. I'm going to be with Bun midterm, and switch to another language (maybe Mojo) longterm.
@@IvanKleshninMOJO LOL. They could not even open source the compiler. Also good luck with your segfaulting runtime and with worse TypeScript UX 😂
@@RustIsWinning 🥱
but... why? What about bun?
bun is much more unstable
What about it?
I looove segfaults
Bun is better
Good one 😂
Meh