A whole website in a single JavaScript file
Since a bunch of people are setting up a straw-man to criticize this post for &quot;not just serving plain HTML&quot; I&#x27;ll share my opinions on this.<p>Almost nobody is going to use Deno to serve a basic HTML site with less than a dozen pages, they are going to use it to build a monolith application to get content from a database, or a service, then generate server-rendered pages, and also host an API from the same codebase, or something similar.<p>Setting up a monolith application means using something like Ruby-on-Rails, Django, Spring, ASP.net, or rolling your own with a Node.js backend serving a SSR front-end, or hydrating React views.<p>If you haven&#x27;t experienced this already, you will come away with one of two conclusions.<p>1. Wow, this is so much fun, as long as I stay on the happy path of ... Rails ... Django ... ASP.net.<p>2. Wow, setting up all these moving parts really sucks&#x27; I&#x27;m mostly writing configuration files, and then Googling the error messages when I inevitably screw something up.<p>What I think Deno is trying to do is make the process of getting a server side rendered application with modern tooling running with minimal ceremony, while still enabling the developer to customize the system and build things that are not covered by the documentation guides. In addition, their solution is one that can be more easily hosted on edge servers than most other options out there.<p>I&#x27;m glad they are doing it, because it&#x27;s a sorely lacking area of modern web development. They only other people who are taking this on in a meaningful way that I am aware of are Remix. I would be happy for there to be more entrants into this field.<p>Best of luck to everyone out there.