Platform · 2000–2015 · Web Boom
Subversion (SVN)
Centralized version control that replaced CVS for enterprises — then git ate the default.
Why Subversion (SVN) faded
Subversion faded because distributed workflows, cheap branching, and GitHub gravity made central servers feel like a tax. It stuck in regulated shops with slow migrations. The idea of atomic commits stuck; the client-server default did not.
Compare with
Related
Platform · 2005–now
Git
Distributed version control that ate the industry. Merge pain remains; centralized SVN does not.
Platform · 2011–2023
Jenkins
Plugin palace CI that defined pipeline culture — and Groovy nightmares. Still running somewhere in your org; greenfield moved on.
Language · 1995–now
Java
Write once, run everywhere — then enterprise forever. Still the backbone of serious backend estates.