5 Amazing Deno Features

Here are five reasons you should check out Deno.
0:00 Intro
0:40 Native TypeScript support
1:17 Built on web standards
2:02 All-in-one built in tooling
2:58 Secure-by-default
3:45 Simplifying cloud development
Resources:
- deno.com/
- github.com/denoland/deno

[@ego-lay_atman-bay]

Dam, that fireship thumbnail got me.

[@TRLYx]

Deno for President!

[@simpingsyndrome]

of wakanda!

[@sayedulkrm]

Deno is Great ❤️❤️

[@pavlovalor]

There is NO such thing as TS runtime. It’s still JavaScript under the hood.

[@ErmiaCodev]

Much luv 4 Deno❤🔥

[@anggoran7398]

Deno really needs community effort to make more docs & tutorial

[@pookiepats]

nonsense, deno by example exist on the site go actually look at it

[@mettle_x]

Wow. Deno channel doesn't disappoint. Becoming a fan ❤

[@pctops]

Para los que no saben que aprender luego de aprender JS, Deno es el paso más natural, es increíble

[@moveonvillain1080]

Show me a job posting

[@user-xo9ks9bc6j]

Great! Thx!!!!! 🌍

[@Sarfarazzamani]

I have a question. Did you ban some countries from accessing your website? I can not go to your website/Docs even with a VPN!

[@lolidkstudio]

Why should we use Deno over Bun?

[@sambaotaku]

Because you can deploy it 😂

[@FullStackJack]

Great video 🎉 deno is a nice experience

[@KelvinWKiger]

❤

[@dilshodturabov]

Is this video response to bun?

[@XceptionalBro]

I do use deno, mostly for fast prototyping, but I have a few products in production using deno. My biggest problem with Deno is how weird string encoding is

[@deno_land]

say more?

[@bryson2662]

Deno is much better than Node but I'll still keep doing Bun for now

[@kvelez]

Cool

[@juk98765]

Why not bun?

[@curetothecommoncode5921]

I love the concept of deno, but idk, for me it's been a nightmare coding in deno in the sense that the intelisense is slow AF/ broken when writing in vscode on a Windows machine

[@korigamik]

You’re working at Debo now?!!

[@_zetrax]

DEVELOPERS DEVELOPERS DEVELOPERS 😂

[@seannewell397]

intro is interesting - learn what exactly? Isn't a staple feature of Deno / Bun is "it's just javascript" so I don't have to learn _anything_ to bring my apps?

[@lucaslopes1260]

They all run javascript. Whether it's Node, Deno or Bun, it won't make a difference in this regard. But if you use some server specific API, then you're bound to find some differences between them.

[@jak4596]

Why don't bun ? Why do you ignore bun ?

[@DevinRhode2]

I can't install it on my corporate laptop in a corporate network. I mostly don't open my personal laptop now that I have kids. Would love to be able to npm install it!!

[@DevinRhode2]

Maybe I could get started developing with it inside a cocker container. But I'm not pioneering a path for a company I don't work for ;)

[@bilatungdulang9708]

I am using bun, btw

[@kasper369]

I am torn between deno or bun for my next project

[@moveonvillain1080]

One which gets the job done.... See end-user doesn't give two craps about what tool you used. Only care about what is made

[@nimitsavant3127]

Hey is that Awesome. heheee

[@KoenVerheyen]

Crackford???

[@pierbover]

It's not really a TypeScript runtime. The execution is still done in JS.

[@thecoolnewsguy]

Exactly. No type checking on runtime.

[@yetzt]

Ah, deno. The runtime that wants to be what bun actually is.

[@Jebusankel]

Dishonest quoting of Douglas Crockford. He believes the reasons to move past JS are all things TypeScript doesn't fix, and his language Misty that he proposes as a replacement is dynamically typed.

[@MommysGoodPuppy]

It's much more nuanced, Crockford thinks the actor paradigm is the future. You can do actor programming in both ts and js. In fact Im working on actor programming with typescript and typescript has been essential in creating Misty like functionality

[@frazuppi4897]

use bun!

[@gokljr]

They are trolling their own previous product 😂

[@evccyr]

Bun is faster than deno

[@owofied_]

But not as good as deno :)

[@jellyfish1772]

Brah😂😂😂😂

[@megakopate]

TS runtime... If you absolutly need types in your backend you should go for a language natively typed.

[@coder_one]

Deno has a nightmarish way of managing dependencies and packages and their versions.
VSC with the official plugin for Deno can't do a good job of prompting for imports of dependencies added to the project.
Widely used tools from the npm world rarely support Deno, not to mention preferring Deno over Node.
The documentation page is confusing, unintuitive and can confuse.
Deno lacks an active community, including a noticeable and engaged community for Deno education.
Until this changes, Deno will be a technology fringe, just as it is now - it is so bland that no one mentions it when JS runtime environments are mentioned.
It's hugely unfortunate, but these are the facts. ;(

[@deno_land]

deno supports npm packages - you should give it a try

[@coder_one]

@@deno_land After all, that's completely beside the point!
I really would have to be quite a confabulant to write all this without personal experience with Deno. I have spent many hours with Deno.
What I wrote in piervous comment are Deno real pains. What I wrote are the real reasons why I exclude Deno from the commercial projects I do.
Node is not perfect. It has a huge number of flaws that Deno, despite its promises, does not solve.
I really encourage you to re-read what I wrote. This is not unfounded hate.
I am realistically saddened that the only places where I can use Deno is Proof of Concept, because it saves me a ton of configuration work that is necessary on Node.js. I repeat - I wrote out the reasons why this is so in my first comment, and I still trust deep in my heart that someday the situation will change.
Unfortunately, as a pragmatist - it is easier for me to assume that sooner Bun will succeed than Deno.

[@vatmanzlokuz680]

@@deno_land tried for use some orm, and fails 😀, also i dont wanna use prisma with proxy