crowlKats
Joined 5 years ago
Karma
38
Submissions
25
Member since
Feb 17
Recent submissions
Comment · 4 months ago
apologies, this is inaccurate currently, will get things updated
Comment · 9 months ago
could you try again? it should be available now (no need to update deno CLI)
Comment · 2 years ago
it actually does: its not part of the WebGPU API directly itself, but its separate: https://deno.com/blog/v1.40#webgpu-windowing--bring-your-own...
Comment · 2 years ago
yes, the doc.deno.land is relatively outdated and uses an old system. our static generator via the doc subcommand and registry are the newer systems
Comment · 2 years ago
Hey, Leo from Deno here.
We recently released a static HTML documentation generator via our `deno doc` subcommand.
We also have a similar system for our registry (here an example: https://deno.land/[email protected]/http/mod.ts?s=Server).
But we have an outdated system for general use, which is similar to what you have built: https://doc.deno.land/.
Did you know about this, and did you want to built your own system regardless, or did you not know about it and would this have been something you would have used instead of creating your own system?
Comment · 4 years ago
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
Comment · 4 years ago
ARM64 builds are something that has been getting investigated. The biggest problem is that github doesnt provide any ARM64 runners, so workarounds around that are necessary
Comment · 4 years ago
deps.ts is currently the most common way, however new projects like fresh use import maps. the problem with importmaps is they are not composable, as such, using an importmap for a library is usually bad as said importmap is not picked up and used, so the end-user would have to add their own importmap with entries compatible for the library (this is what fresh does: it generates an importmap with entries it needs). due to this problem, deps.ts is the most common solution, however I do hope that composability issue with importmaps will change.
Comment · 4 years ago
proper applications as well. example is the https://deno.land website has an average CPU time of 6ms. CPU time means it doesnt include any IO bound operations, so ie doing a fetch request wont really contribute to the CPU time.
Comment · 4 years ago
The wording in that blogpost might be a bit off, here it is more in-depth: https://deno.com/blog/netlify-edge-functions-on-deno-deploy
Netlify is using Deploy
Comment · 4 years ago
The M1 builds are made manually by us, as github doesnt provide any runners. the same problem does apply for linux arm, however we don't have any arm linux systems any one of the members use; and building on a pi is a no-go, as that can take 70+ minutes, so that would make our release cycle a lot more complicated. Either way, we are investigating potential possibilities besides waiting for github to have runners available
Comment · 4 years ago
No, Netlify actually uses Deno to some degree: https://www.netlify.com/blog/announcing-serverless-compute-w...