The video on the page doesn't have controls and I have Firefox block autoplay; fortunately, I can just right click and select play from context menu.
Just giving notice.
Deno 1.27
11–20 of 71 posts
Re: Deno 1.27
#12Excited for the improvements, some big wins there! But surprised to see so many removals in the Changes section to what seems to be a minor version of a 1.x release. Nothing that hurts me personally, altho not Semantic Versioning and cautions shaky ground to build on?
There are no removals in the CLI, and std is considered unstable, and due to that has different versioning that is still in 0.x
Re: Deno 1.27
#13Link to cached blog post: https://readwise.io/reader/shared/01ggdaqh2rr2my3qc5rzw09kpw
Re: Deno 1.27
#14Better IDE support is huge. I know a lot of devs who liked the idea of Deno but weren't in a position to dump a lot of their development tooling to pick it up, so this effectively removes a big barrier to adoption for a lot of folks. Excited to see how well Deno's security features pan out under broader, real-world usage.
As a side note, this comment in itself is interesting. We are seeing tighter integration between frameworks and IDEs, almost a reversion back to early visual studio days. Will be interesting to see how each nudge the other.
The coupling here is actually extremely loose. It's based around implementing an LSP server, which is editor/IDE agnostic. It trades depth of integration for breadth of support. I think it's the total opposite of the old days!
Re: Deno 1.27
#15Re: Deno 1.27
#16I'm an eager and early adopter of Deno. I however look forward to ecosystem improvements, and the interop with npm is helpful. I was working on a side project recently that was a simple CRUD app and I just ended up going with Express on Node after fighting with Oak on Deno for a few days. It was still in the way enough to slow down the rapid fire development process that happens when you're still figuring out an idea…
I'm also dipping my toes in Deno (with Fresh) for a side project. Just curious, what were the blockers you came across with Oak?
Re: Deno 1.27
#17Better IDE support is huge. I know a lot of devs who liked the idea of Deno but weren't in a position to dump a lot of their development tooling to pick it up, so this effectively removes a big barrier to adoption for a lot of folks. Excited to see how well Deno's security features pan out under broader, real-world usage.
> I know a lot of devs who liked the idea of Deno but weren't in a position to dump a lot of their development tooling to pick it up if VS Code already supports TypeScript, what is missing?
Deno has its own language server, unfortunately. This is necessary because of a few key aspects of Deno code that are incompatible with the regular TypeScript support, and it means Deno's editor integration is often a step behind mainline TypeScript
Re: Deno 1.27
#18Nice! Time to upgrade.
Re: Deno 1.27
#19As a Jetbrains user, somewhat annoying to see everything in VS Code.
An editor is an editor, why on earth would it bother you that someone uses a different editor than you?
Re: Deno 1.27
#20As a Jetbrains user, somewhat annoying to see everything in VS Code.
Our editor integration is completely editor agnostic. Deno implements the Language Server Protocol [1], which essentially all editors support. Because of this the new inlay hints feature, is supported on all editors that support inlay hints and use our LSP integration. The Jetbrains integration for Deno uses our LSP, but I don't know if they support inlay hints yet. You can find docs on using Deno LSP with other edit…
I've been using Deno on neovim and it's been a breeze