Ha, in what I believe Ryan's first talk about Deno, he mentioned something about avoiding cute features or so, then he said Deno has URL-based imports "because they're cute". It didn't take long for someone to raise it up in 2018:
It's slightly annoying to me that the messaging around this, including in this article, seems to be a bit all over the place.
What was always actually cool about HTTP imports, and several other Deno features, was browser parity. And I applaud their choice to follow the import map spec for the same reason, instead of inventing a new custom manifest format.
So to me the real message should be "well, we have to have HTTP imports, because that's how the web works. But that doesn't scale to this-or-that use case, so here's what we've done to help with that"
Comments
Ha, in what I believe Ryan's first talk about Deno, he mentioned something about avoiding cute features or so, then he said Deno has URL-based imports "because they're cute". It didn't take long for someone to raise it up in 2018:
https://github.com/denoland/deno/issues/195
We've come full circle :)
It's slightly annoying to me that the messaging around this, including in this article, seems to be a bit all over the place.
What was always actually cool about HTTP imports, and several other Deno features, was browser parity. And I applaud their choice to follow the import map spec for the same reason, instead of inventing a new custom manifest format.
So to me the real message should be "well, we have to have HTTP imports, because that's how the web works. But that doesn't scale to this-or-that use case, so here's what we've done to help with that"