Can anyone speak to whether this is likely to succeed on its merits, or point to analysis of same by competent professionals?
Obviously, it looks like a pretty egregious case of Oracle-ness, but it's the job of Deno's lawyers to make it look like that. I'd be interested to see disinterested commentary.
Claim #2 is particularly egregious. If it actually has merit, and if a judge is willing to hold a large corporation accountable for breaking the law (lol), someone at Oracle needs to be charged and prosecuted for it.
Didn't know about Oracle using Node as an example of them building/selling things utilizing the "JavaScript" trademark. I think the post's framing of this being fraudulent is accurate, but even if it didn't legally qualify, it is at the very least extremely dishonest and unethical.
It’s not “obscure” or “exotic;” at least, no more than Node was when it was released. Honestly this is such a lame take to those of us who are working in JS outside of Node and Deno.
And people do work at that intersection.
IMO Deno is the worst option of all new JS runtimes and taking on this fight kind of makes sense that way. If you can’t win mindshare, start a fight. I guess. (In my opinion they should have simply designed Deno to be NPM compatible, but here we are.)
Only recently... and yes, to Deno's great credit. Deno has an amazing team and this isn't commentary about their hard work; just disagreement with one of the early decisions.
Neat. But for a relevant query, try searching for "npm" instead. 0 issues listed. Further, in the `deno_npm` repo for npm resolving by the deno cli, there are two open issues. One is a feature request, and the other is not clearly an important issue.
Related:
Oracle, it's time to free JavaScript (277 points, 70 days ago, 127 comments) https://news.ycombinator.com/item?id=41557383
Deno is filing a USPTO petition to cancel Oracle's JavaScript trademark (7 points, 3 days ago) https://news.ycombinator.com/item?id=42212949
Can anyone speak to whether this is likely to succeed on its merits, or point to analysis of same by competent professionals?
Obviously, it looks like a pretty egregious case of Oracle-ness, but it's the job of Deno's lawyers to make it look like that. I'd be interested to see disinterested commentary.
Claim #2 is particularly egregious. If it actually has merit, and if a judge is willing to hold a large corporation accountable for breaking the law (lol), someone at Oracle needs to be charged and prosecuted for it.
Didn't know about Oracle using Node as an example of them building/selling things utilizing the "JavaScript" trademark. I think the post's framing of this being fraudulent is accurate, but even if it didn't legally qualify, it is at the very least extremely dishonest and unethical.
This is either for the greater good of the whole JavaScript community or a PR stunt to just get in the news. Or both.
GraalJs, it would seem, would count.
It’s not “obscure” or “exotic;” at least, no more than Node was when it was released. Honestly this is such a lame take to those of us who are working in JS outside of Node and Deno.
And people do work at that intersection.
IMO Deno is the worst option of all new JS runtimes and taking on this fight kind of makes sense that way. If you can’t win mindshare, start a fight. I guess. (In my opinion they should have simply designed Deno to be NPM compatible, but here we are.)
Deno is NPM compatible
Only recently... and yes, to Deno's great credit. Deno has an amazing team and this isn't commentary about their hard work; just disagreement with one of the early decisions.
`is:open is:issue label:bug label:"node compat"` -> 203 issues currently open.
Neat. But for a relevant query, try searching for "npm" instead. 0 issues listed. Further, in the `deno_npm` repo for npm resolving by the deno cli, there are two open issues. One is a feature request, and the other is not clearly an important issue.
> Neat. But for a relevant query, try searching for "npm" instead
`is:issue is:open npm` 467 open
https://github.com/denoland/deno/issues?q=is%3Aissue+is%3Aop...
`is:issue is:open label:bug npm` 199 open
https://github.com/denoland/deno/issues?q=is%3Aopen+is%3Aiss...
For the record, "NPM compat" probably does include many feature requests (legitimately), not just bugs.
Good luck