The Future of the Web Is on the Edge
As much as I love Deno, I think this is the wrong way to frame it. For a number of reasons.<p>1) Sure, big web apps for a global audience would benefit from a distributed application and distributed data. But, honestly, most web apps I've worked in my 20+ years in web dev have been for an audience in a single country or even city.<p>2) It's easy for Deno to say "get a distributed app running at the edge!" when the hard part is having distributed data which they don't solve. If you don't need distributed consistent data then you're probably more than fine with a monolith with a CDN.<p>3) Those latency numbers don't seem right to me. My production server in AMS returns a response in 200ms to here (central Mexico).<p>4) Performance evangelists and salesmen will try to convince everyone they need to get a response in 50ms, but for most use cases that's just ridiculous. Most people are fine getting a response in under a second. Just use a CDN for your static assets and your monolith will be fine.<p>The edge is cool, but it's not "the future". It's just another tool with pros and cons.