Yeah, I've seen worst API documentation, but their docs site is needlessly weird. Documentation is something that should be solved by now. No project needs wh

Yeah, I've seen worst API documentation, but their docs site is needlessly weird. Documentation is something that should be solved by now. No project needs whatever custom thing Deno uses. I don't get it. Leaving out details, for the most part, is the right approach for now, I think. Only Node/JavaScript veterans should probably be using Deno for the time being. But I definitely hope Deno can eventually take over and make Node obsolete. > 2) The VSCode extension still needs work. It’s usable, and better than nothing, and it’s better than it used to be, but (ordered from most to least significant) At this point, I've kind of given up on VS Code language/runtime extensions in general. Virtually none of them work with the slightest variation in toolchain configuration, whether it's C++ or Typescript or even ESLint. You're lucky if they don't slow the heck down over time. Import paths are the worst! Somehow that's something I inevitably run into, again, no matter the language. I kinda want to blow all this stuff up and start over. Maybe Deno is a part of that equation. haha