Gregory's Server
Deno 2 Release Candidate has dropped:
‣ Add `process` global variable, remove `window`
‣ Improve dep management
‣ Permission system updates
‣ Many stabilizations
‣ Better CommonJS support
‣ Test documentation with `deno test --doc`
|
7 posts total
Show previous comments
 @deno_land am I the only one that doesn’t see any issue with this? From the page: > Unlike typical trademark holders who protect their trademarks by extracting licensing fees or enforcing usage restrictions, Oracle has allowed the JavaScript name to be used by anyone. Doesn’t that mean you should just ignore the trademark? Imagine the confusion that would arise if a random third party created "Javascript Conf". Deno 1.46 is not only the last 1.x release, but also one of the biggest: #Deno 1.39 is released! - WebGPU support Read more:   @deno_land What I actually want is for you to give me the source code to Deno Deploy, because I don't trust that you won't censor my users.
|
@deno_land I guess there are no plans to fix importing from source, and broken local development, with the new JSR/deno.json package stuff prior to Deno 2.0? seems a glaring oversight to me
[1] https://github.com/jsr-io/jsr/issues/133#issuecomment-2274239545
[2] https://dbushell.com/2024/08/09/jsr-and-deno-final-review/#deno-ish
I don't understand why Deno didn't just go full adoption of package.json and copy Node, it's objectively superior.