
2000–2009
Web Boom
The browser ate the desktop
The web became the default delivery surface. LAMP and Rails made shipping cheap; Ajax made pages feel like apps; SOAP/SOA tried to enterprise-ify the wire. REST won by being debuggable with curl. This decade invented the modern product cadence — and the habit of treating every new framework as destiny.
27 technologies in this era
Language · 1991–now
Python
From scripting glue to the default language of data and AI. Readability as a growth strategy.
Architecture · 2000–now
REST / HTTP APIs
Resources over RPC theater. Won the API wars by being boring enough to debug with curl.
Platform · 1991–now
HTTP / HTTPS
The application protocol of the internet. HTTP/2 and HTTP/3 are evolutions, not replacements.
Platform · 2005–now
Git
Distributed version control that ate the industry. Merge pain remains; centralized SVN does not.
Framework · 2005–now
Django
Batteries-included Python web. Still the adult choice when you want an admin, auth, and ORM that behave.
Architecture · 2004–now
MVC web frameworks
Model-view-controller as the default web shape. Still how most server-rendered apps think.
Framework · 2003–now
Spring
Java's practical operating system for apps. DI and Boot made enterprise Java shippable again.
Architecture · 1998–now
LAMP
Linux, Apache, MySQL, PHP — the cheap, fast path to a website. Mutated into countless managed stacks.
Language · 1995–now
PHP
Dismissed by snobs, powering WordPress and half the web. Ugly pragmatism beats elegant irrelevance.
Framework · 2004–now
Ruby on Rails
Convention over configuration. Taught a decade of frameworks how to ship MVPs — and how to hit scaling walls.
Framework · 2010–now
Flask
Small Python core, extensions for everything else. The pragmatic counterweight to Django's batteries.
Architecture · 2005–now
Ajax SPAs (early)
Partial page updates without full reloads. Became the mental model for every modern front-end framework.
Practice · 2001–now
Agile (as practiced)
Individuals and interactions — then SAFe slideware. The manifesto stuck; the ceremony industrial complex is the fad layer.
Framework · 2011–now
Bootstrap
Opinionated CSS that made every site look like a startup for a while. Still the fastest path to a decent admin UI.
Language · 1987–2010
Perl
The duct tape of the early web and sysadmin era. Regex culture in a language that read like line noise.
Framework · 2007–now
Sinatra
Minimal Ruby routing for apps that did not need all of Rails. DSL elegance in a few hundred lines.
Framework · 2006–now
jQuery
DOM peace treaty for a fractured browser world. Mission accomplished — then frameworks ate its job.
Platform · 1995–2015
ColdFusion
Tag-based rapid web apps in CFML. Government and agency sites that outlived every contractor who knew the syntax.
Architecture · 2000–2016
SOAP / WS-*
Enterprise web services with ceremony. Interoperability theater with XML envelopes.
$ Banks and governments sunk fortunes into WS-Security, WSDL toolchains, and vendor stacks — then quietly rebuilt on REST/JSON while still paying maintenance on the old bus.
Architecture · 2003–2015
Enterprise SOA
Reuse via shared services — in theory. In practice: central buses and political ownership fights.
$ ESBs, governance boards, and "service portfolios" burned seven-figure programs. Many orgs got distributed monoliths with worse latency and a permanent integration team.
Framework · 2010–2016
Backbone.js
Minimal structure for early client MVC. Taught the browser to think in models before React rewrote the rules.
Framework · 2010–2016
Knockout.js
Observable view models for declarative UI. MVVM before the term became enterprise cosplay.
Framework · 2006–2017
Google Web Toolkit (GWT)
Write Java, compile to JavaScript. Enterprise AJAX before anyone admitted they hated JavaScript.
Framework · 2007–2018
Ext JS / Sencha
Enterprise desktop UI in the browser — grids, trees, and megabytes of widget chrome.
Architecture · 2002–2016
Enterprise Service Bus (ESB)
Message bus in the middle of everything. SOA's plumbing invoice with vendor licensing.
$ Middleware vendors sold central buses that became single points of failure and political bottlenecks. Integration teams grew; end-to-end latency did too.
Platform · 1996–2020
Adobe Flash
Animations, games, and video in a plugin the web learned to hate. Steve Jobs wrote the obituary; HTML5 dug the grave.
Framework · 2007–2013
Silverlight
.NET in the browser via plugin. Netflix used it; the web moved on anyway.
$ Enterprises built internal dashboards and streaming pilots on Silverlight just as HTML5 and iOS said no to plugins. Migration projects burned budgets Flash already warned them about.