It's always worth reading the Deno release notes even if you're not using Deno because it's such a fascinating collection of interesting ideas.
I always learn something new from them.
In this case it was the existence of the URLPattern web API: https://pr8734.content.dev.mdn.mozit.cloud/en-US/docs/Web/AP...
Also that Mutual TLS is an alternative term for client authentication.
One of the most exciting opportunities IMO that Deno opens up, compared to most traditional server-side frameworks, is the possibility for simple url-based live-reload workflows in production.
I'd love to be able to develop backend services by pushing source code to some url as I develop, and then have the production instances of the service notified of the changes and reload themselves immediately for a super-tight feedback loop.
In theory, building this kind of workflow in Deno should be very feasible, so I'm hoping to give it a shot in the not too distant future, but I'm wondering if anyone else has already tried it?
Does anyone know if Deno has undergone a security audit yet? I'm interested in using it as a sandbox to run user-submitted JS, and I know its permission model is powerful, but I don't know if it is formally certified (if that's even a thing) and if you can prove that there can't be some exploit that can be used to break out of the sandbox.
Funny, I was just looking into whether I could add a Deno config file to my project. Nice to know this was just made possible!
Love Deno and using it as a node replacement. Fantastic work. I encourage anybody who has npm packages to move everything to deno.
Only tangentially related, but what's the point of a static class block? What problem does it solve that's not covered by either the class constructor or a static const? Doesn't it introduce a weird (stateful!) computation that's hard to reason about?
There's probably a use-case I'm missing, because intuitively I'd automatically classify it as bad a practice.
https://github.com/denoland/deno/discussions/11771
> NodeJS compatibility, what is our high-level strategy, goals, next steps?
> Do we see Node and Deno co-existing, or do we want to think of Node as "legacy"? (Note, there was no clear decision on this question, it was just a conversation)
> If we could say "you can run your Express server under Deno faster than Node" would that encourage adoption? No clear answer
I really wish they go for a better compatibility with Node and sell themselves as a replacement that is strictly better.
Deno is awesome, and it's great to see the WebCrypto additions!
My current top feature request is that I wish Deno would have the same permission model for the repl.
I highly recommend listening to this recent podcast with Ryan Dahl: https://changelog.com/podcast/443
Deno is really awesome for shell scripts. Forget Bash. Forget Python. Deno is way better.
You get a fairly sane type system, good performance, easy deployment (it doesn't count as easy if it's a pain on Windows), supports single file scripts with third party dependencies, and no compilation to deal with.
There aren't really any alternatives that offer all that as far as I know.
I'm convinced to try deno. I only use node for small testing scripts so it should be easy enough.
> This release allows deno lint and deno fmt to be configured.
That's good news. The main thing holding me back from seriously looking at Deno was the lack of config for the formatting. The default settings weren't right for me, and I tend to avoid projects where you have to fight the tools. I'm going to take another look now.
Anyone using Deno in production? Would love to hear how it's going for your team.
I know it's a bit superficial, but I love Deno's branding. Their logo is cute and evokes a sense of calm, and the variations on the mascot are nice.
Looks good. Interesting that they are "bringing back" mutual tls (after browsers pretty much axed it..).
Is there support on the (deno http) server-side too? Eg: easy to set up mutually trusted, private-/non-ca tls between a deno client and deno server? Perhaps via a self-signed/private CA?
Does anyone know of providers for running deno FAAS style? Or is a VPS needed?
How it is the zero-copy ArrayBuffer transfer function implemented?
My son is 13. He loves Deno. What I don't get is why a 13-year-old can get Deno, and we don't, and it's not as widely popular as it must be for its merits!
you got me at no need for scaffolding files babel.config.js
Why’d they have to give a JS environment the name of a guido.
How many runtimes are there for JS? They seem to pop up once a week...
I tried out Deno last weekend for a fun little hack project (syncing a local Markdown file to a formatted Google Doc), and it was awesome.
Writing TypeScript code for Deno feels a lot like writing Go (which is a very good thing to me):
- opinionated build/fmt/deps
- well-designed stdlib
- no need for scaffolding files (.eslintrc, babel.config.js, jest.config.js, mocha.opts, etc.)
If that sounds good to you, try Deno!