| ▲ | pjmlp 6 hours ago | ||||||||||||||||
Trying to pull people away from reference tooling requires lots of investment and historical has always failed. Eventually the reference implementation gets good enough, and that is it. In JavaScript case, the first error was to ignore compatibility with native addons and existing nodejs modules. The second was not providing a business value why porting, with the pain of compatibility, one because "it feels better" doesn't release budgets in most companies. | |||||||||||||||||
| ▲ | philipallstar 6 hours ago | parent [-] | ||||||||||||||||
In this case I think the reference implementation was created by one of the deno founders. | |||||||||||||||||
| |||||||||||||||||