IDK, I think this is getting overstated. Don't forget - there's very typically a runtime environment available that's a lot closer to the user... their browser

IDK, I think this is getting overstated. Don't forget - there's very typically a runtime environment available that's a lot closer to the user... their browser. The edge, as a place to run code, is a bit of a tweener... farther from the user than the browser, farther from the data than the database environment. If the data the edge needs is also on or near the edge, you can really start to do something with it. But that means your data is distributed. You want to have a really solid plan on how your edge data is kept valid. That's not so hard with static assets but edge processing on static assets seems like a relatively narrow case, because it needs to make more sense than pre-computing all the cases and just having a more static files. Edge processing on dynamic data is pretty interesting, but having coherent distributed dynamic data tends to be app specific and hard to get right and keep right. There are certainly cases, but I don't think they usually tend to comprise the whole app. I think it will usually be a partial solution and add a bunch of complexity, so apps will want to use it sparingly, where it's really needed. I think this will be more of a tool in the toolbox, not the general future of the web.