Yes, it's cool and all that it's "blazing-fast". And for brand-new projects with small teams, it's probably totally sufficient. But IMO it's one of the biggest roadblocks to Deno being used for Serious Business.
Having robust linting/styles rules is crucial for robust development teams. All the established companies for whom I've worked spent years honing their ESlint rules. But most of these rules have no Deno equivalent. You can only replace ESlint with Deno Lint in fairly simple use-cases, and can't really use ESlint on Deno projects (despite my best efforts).
Even though Deno is great, even though the code "works", the inability to granularly enforce styles across a development team is a deal-breaker. Honestly the fact that the Deno team kind-of reinvented a wheel unnecessarily with Deno Lint feels like NIH (Not Invented Here) Syndrome, which is super disappointing given the respect I have for Ryan Dahl and the rest of the team.
@dsherret It's really good to have this context! Thanks!