Deno 1.40 introduces the Temporal API, TC39 decorators, and a range of deprecations and stabilizations, along with improvements in Node.js compatibility, LSP, diagnostics, and handling of unstable features, paving the way for a seamless upgrade to Deno 2.
This is an ultra-fast #NodeJS, #Bun, and #Deno interface to LMDB - leaves all other DBs in the dust. Your screen isn't wide enough to show how fast it is...
I can't believe Deno gets you a testing framework AND coverage reports without any additional downloads. 2010's me would have killed for something like this instead of the weird soup that was mocha and sinon no wait now let's use jest oh and don't forget nyc er wait it's istanbul now and...
Hello TypeScript WebAuthn devs, I'm happy to announce the release of SimpleWebAuthn v8.3.7! This small release includes some newly exported classes and types for easier integration with your projects. Check out the CHANGELOG for full details 🚀
@baldur Another issue with npm modules in #Deno is that many #npm modules just break under restrictive permissions. They expect to have read access to the whole disk and break if you deny them that. So you pretty much have to grant every permission, but of course that defeats one of the major advantages of using Deno: prevent bad modules from doing bad things.
There may be ways to improve that over time, but it's not a pretty picture.
@baldur I share a lot of your concerns. I think #Deno as a project has good ideas and it’s been a joy to work with as part of @silverbulletmd. My concerns, similar to you:
Are they taking up too much at the same time given their size?
Monetization expectations must be significant and hard to deliver given their VC funding. And if they don’t, what then?
Ryan Dahl's #Deno Weekly Update video just dropped that includes pointing out a new course on how to use LangChain.js with Deno Jupyter notebooks to explore LLM's on deeplearning.ai, the availability of Deno on Termux running on Android, and changes coming in version 1.40 including implementing import.meta.dirname and import.meta.filename to replace Node's __dirname and __filename. Version 1.40 is scheduled to be released on January 25. @deno_land https://youtu.be/adb414xtBe8?si=PsNaFChmIZFaRfVC
I can’t vouch for #Deno in a high scale, public web environment, because I’m not doing that stuff at the moment, but it’s nice for intranet apps. I’ve been using it for years now. It’s solid.
It’s MIT licensed so good escape hatch if VC funding starts to push the project in the wrong direction.
Because #Deno is mostly web & browser-compatible API at the core, you can use it without taking a big dependency on proprietary or non-standard API. I don’t use other people’s libraries and have a tiny dependency on Deno core file system APIs and the web request handler so can move easily if necessary. Works for me.
Deno 1.40: Temporal API (deno.com)
Deno 1.40 introduces the Temporal API, TC39 decorators, and a range of deprecations and stabilizations, along with improvements in Node.js compatibility, LSP, diagnostics, and handling of unstable features, paving the way for a seamless upgrade to Deno 2.