3 ms·

Has anybody here used Deno recently? I tried it out at 1.0 and it was... a little bit rough. Basic APIs like fs weren't stable yet, the documentation on how to

Has anybody here used Deno recently? I tried it out at 1.0 and it was... a little bit rough. Basic APIs like fs weren't stable yet, the documentation on how to import them was out of date, there were multiple VSCode extensions and it took a couple hours to get one of them working properly. Of course these are all relatively easy things to smooth out over time so I'm curious what the experience is like now.

searchableguy 6y ago
It's pretty good. Deno provides LSP now which is what Vscode extension use. Other text editors also work with deno since they can use LSP. I haven't had any problems with fs APIs. They provide almost everything and any nice utilities can be imported from std. Testing has gotten a lot better. Bundling and compiling works too. Support for third party platforms such as vercel, heroku, and other platforms is decent. Many rails-like frameworks are also popping up. Overall, I am satisfied.
- brundolf 6y ago
  To be clear: IDE support existed and worked fine once I got it going. It just wasn't a smooth experience out of the box; I had to do some digging on Google, fiddle with the configuration, hunt for answers in GitHub tickets, etc. For a runtime whose main appeal (for me) was no-hassle TypeScript, all the hassle put a pretty big damper on things. Glad to hear things seem better now
  - searchableguy 6y ago
    Today, you can run an init command on Vscode to initialise a deno project. It should work smoothly from there. It provides auto completion for registries and code lens for external code which was missing before, I think when you used it.
mattlondon 6y ago
I've not used it professionally for anything yet but I have been hacking around with it on the side for fun (I've recently created a Gopher protocol client and added it as a Third Party module: https://github.com/matt1/deno-gopher https://github.com/matt1/deno-gopher / https://deno.land/x/gopher@v0.0.5-alpha https://deno.land/x/gopher@v0.0.5-alpha - it has been a fairly enjoyable process) On the whole I have been quite happy with it - the VSCode support is now pretty good (and even without proper integration it was still fully usable even if I didn't get intellisense and had some red squiggles around the imports etc), and sounds like this release will improve it even more. I do agree though that the documentation is a bit sparse - the auto-generated docs are nice enough, but it could benefit a bit more from some more coverage of human-generated docs for some of the more common use-cases... that will come with time I guess. My main criticism is that the built-in test framework is a GREAT thing to have, but it does not have support for mocking or spies so it is limited in real-world usefulness. E.g. in my Gopher protocol client, there is not an easy way to mock out the `Deno.connect` built-in function to create a TCP socket so it is hard for me to test failures at the TCP level. I am sure with some gymnastics I can abstract everything away under layers of interfaces and classes and manually inject everything to make testing easier, but it would be nice to just be able to mock/spy out functions/classes rather than have the entire architecture of the project be dictated by the testing framework. There are third-party alternatives that can be used, but I'd prefer to stay as close to "standard" as possible.

searchableguy 6y ago

It's pretty good. Deno provides LSP now which is what Vscode extension use. Other text editors also work with deno since they can use LSP. I haven't had any problems with fs APIs. They provide almost everything and any nice utilities can be imported from std. Testing has gotten a lot better. Bundling and compiling works too. Support for third party platforms such as vercel, heroku, and other platforms is decent. Many rails-like frameworks are also popping up. Overall, I am satisfied.

brundolf 6y ago
To be clear: IDE support existed and worked fine once I got it going. It just wasn't a smooth experience out of the box; I had to do some digging on Google, fiddle with the configuration, hunt for answers in GitHub tickets, etc. For a runtime whose main appeal (for me) was no-hassle TypeScript, all the hassle put a pretty big damper on things. Glad to hear things seem better now
- searchableguy 6y ago
  Today, you can run an init command on Vscode to initialise a deno project. It should work smoothly from there. It provides auto completion for registries and code lens for external code which was missing before, I think when you used it.

mattlondon 6y ago

I've not used it professionally for anything yet but I have been hacking around with it on the side for fun (I've recently created a Gopher protocol client and added it as a Third Party module: https://github.com/matt1/deno-gopher https://github.com/matt1/deno-gopher / https://deno.land/x/gopher@v0.0.5-alpha https://deno.land/x/gopher@v0.0.5-alpha - it has been a fairly enjoyable process) On the whole I have been quite happy with it - the VSCode support is now pretty good (and even without proper integration it was still fully usable even if I didn't get intellisense and had some red squiggles around the imports etc), and sounds like this release will improve it even more. I do agree though that the documentation is a bit sparse - the auto-generated docs are nice enough, but it could benefit a bit more from some more coverage of human-generated docs for some of the more common use-cases... that will come with time I guess. My main criticism is that the built-in test framework is a GREAT thing to have, but it does not have support for mocking or spies so it is limited in real-world usefulness. E.g. in my Gopher protocol client, there is not an easy way to mock out the `Deno.connect` built-in function to create a TCP socket so it is hard for me to test failures at the TCP level. I am sure with some gymnastics I can abstract everything away under layers of interfaces and classes and manually inject everything to make testing easier, but it would be nice to just be able to mock/spy out functions/classes rather than have the entire architecture of the project be dictated by the testing framework. There are third-party alternatives that can be used, but I'd prefer to stay as close to "standard" as possible.