Deno Namespace APIs

[@morkhoudia9]

Deno is the new era. Great tutorial

[@junaga2]

you missed "winter is coming" there 🥺

[@SamuelKarani]

I was almost shocked when she din't type "winter is coming" - nice subversion

[@PaleShadeEntity]

Good Stuff. This would be really great for log files

[@TheNoirKamui]

You have to put a dark mode to the docs! Darkreader doesn't flip the code snippets

[@jonkoops]

Love Dono, great work. I however don't understand why we need to attach all these functionalities to a single global. Is it not the point of modules to do this kind of namespacing?

[@etherxi]

what about threads or coroutine? is there any in built functionalities?

[@benjidaniel5595]

Coroutines are in JS/TS are just generator functions, but still single threaded. However you can use workers to run code in a seperate thread 👍

[@uditagarwal7768]

Honey!! Come here quick. New video from deno is here.🎉

[@ralpha112]

ew

[@vikingshadow4877]

Theme name?

[@parlor3115]

Title should be "Deno Global Namespace APIs"

[@benjidaniel5595]

I really don’t understand why the Deno team chose to slap their APIs right into the Deno root namespace rather than name spacing them like in Node

[@donmorris4506]

Been trying Deno. Not really liking it. Security is annoying. Can’t add local npm packages with file paths. Too much work to create an npm package with dnt. Deno is not worth my time yet.

[@ameliaamare]

Security is often a problem because the default is too permissive. The tradeoffs you make in Deno is well worth it because those are things you should be thinking about regardless. You could always fall back to allowing all but, again, that’s destroys the whole point of already having a simple interface for specifying permissions. Also, have you tried Deno 2? I remembered using a local NPM module by editing the import map and it worked just fine. If it’s not a private package setting the nodeModulesDir flag to auto works quite well for NPM modules now.

[@donmorris4506]

@@ameliaamare yes, been trying 2.0. Disagree about the tighter security. More cumbersome to deal with. Still can’t import a local package. It should be as easy as using npm: npm i ../pathToPackage. It would be best if Deno used a sym link like node. I typically split my domain model code into a separate package when developing a new project that has both a client app and server code. I want it to be file based until I get the project stable. I then convert the package import to use a git reference and version the domain model. Haven’t had success using Deno 2 for my workflow.