Recent searches
Search options
Deno is known for its HTTP imports, but we've found it's insufficient for larger projects. This post explains the situation and how we've improved it.
@deno_land hm. All this reasoning sounds good, certainly, and the problems you identify are definitely real ones I've experienced. But doesn't JSR open up the same door that npm had: that two years from now someone says "hey! why don't we make a JSR company and do an IPO? that sounds like a great idea?"
@sil @deno_land jsr is literally like npm with a different name. there’s nothing new here imo
I don't really think the downsides with HTTP were so bad though. People just weren't ready for decentralized coding, so to beat Bun and Node, Deno has to bridge the gap. It's a little unfortunate because I think Deno is ahead of its time. Issues like semver could be fixed by proposing a standardized URL format for HTTP modules.
I saw someone else who installed ditto posted a screenshot of their server doing it too incidentally
@0461fcbecc4c3374439932d6b8f11269ccdb7cc973ad7a50ae362db135a474dd you are right. HTTP imports is still great (and will always work in Deno — in fact it powers JSR). but for humans and usability and dup deps, having JSR makes it easier.
