[est31]

> This was before AWS and Rails was just getting started, so just getting something up and visible was a major technological effort.

Before rails there was LAMP. That's what Facebook used. Java servlets existed as well. And rented clouds existed before AWS as well. Despite the hype for them on pages like this, neither AWS nor Rails were really big disrupting inventions. The market for both existed before them, and will exist after they've fallen out of favour.

Where innovation happened is in the scaling domain. Terraform, kubernetes, etc, as well as in the SaaS tools you mentioned. But most of those things aren't needed for earliest stage startups. You don't need to be super scalable from day one. You can just run everything from one very powerful box for a while.

Of course this all depends on what your application is. If your product is a cloud based tool to post process movies, it will be a different setting from a CRUD app to plan events.

[wpietri]

In some sense, nothing has been really disruptive since the web browser. But that doesn't matter because what I'm talking about is reduced cost, reduced accidental complexity, reduced systemic latency.

Having lived through it, it's just loads easier to get something up and going these days. I ended up back in some Java code again recently, and servlets are a) a pain, and b) a general-purpose abstraction. They're adequate for a lot of things, but not particularly great at anything. Whereas these days people have had 15 years to come up with special-purpose code to accelerate all sorts of common activities. My point wasn't that AWS and Rails were the only good things that happened in 15 years. It's that those, which now seem old and boring, were near beginning of a whole wave of innovation aimed at making it easy to have a consumer-grade user experience up and running.