Even if port 80 was unprivileged, wouldn't you still run into issues if multiple users attempted to bind to the same port?
Really, what would the problem be with just deploying an nginx instance that listens on 80 and routes by domain?
Really, what would the problem be with just deploying an nginx instance that listens on 80 and routes by domain?
What I want to know is why can't we get all the major web browsers to look for (and honor) SRV records, so that www.mydomain.com can transparently have the browser connect to port 30338 (or whatever port my app is listening on). Then we dispense with the need for proxies altogether.
The point of the article as I understand it, isn't so much about the possibility of shared web hosting - it's obviously possible. It's more about how early design decisions shape our paradigms and the way we understand computing and the necessary resources.
I really like this idea, it's really elegant.