3 ms·

I'm a little confused how the author could come to the conclusion Deno is not ready for AWS Gateway integration, when they openly admit the main reason for this

by zxexz 6y ago

I'm a little confused how the author could come to the conclusion Deno is not ready for AWS Gateway integration, when they openly admit the main reason for this is that Deno is downloading all packages on a cold start, and that there are "probably some mechanisms to speed this up". To their credit, the author does point out another potential flaw in the disclaimers section - the Node.js AWS SDK is optimized for node, and AFAIK they haven't released a version for Deno.

jonny_eh 6y ago
> there are "probably some mechanisms to speed this up". Why would they publish before looking into this first? At best it's incomplete, at worst it's misinforming readers.
- uncletaco 6y ago
  Reminds me of a blog post from a couple of months ago where somebody was writing about "how to do X in emacs". The kicker was they were using doom emacs and didn't understand which packages or functions were actually allowing them to do their thing, nor that doom was highly customized. After getting eaten alive in r/emacs they deleted the post. Hopefully this guy's post stays up and gets an added disclaimer about not writing shit like this without actually deep diving and learning the software they're comparing.