Web Objects was the first web framework I worked in, back in 2001, and I didn't really understand it at the time, but it already had built and running in produc

Web Objects was the first web framework I worked in, back in 2001, and I didn't really understand it at the time, but it already had built and running in production many of the features that I subsequently came into contact with via supposed innovations in other stacks. The J2EE 1.3 spec for example added "entity beans" and unleashed hideous vendor implementations like WebSphere on developers. The impact of all the anti-patterns that spec inspired are still visible in the development world today - I'd say it is indirectly responsible for the rise of Spring and Rails. WO also had the added benefit of being a full-stack solution. The way the J2EE spec was built up of sub-specs really contributed to the fragmented Java framework universe. Developers then had to get used to spending think-time reasoning about the way the pieces and "tiers" fit together and less time building coherent apps.