I can believe that, but I recall some tradepress article about more than 100 companies selling non-java 'web middleware' who got bowled over by J2EE, and otherwise Next would have just been another one of those. That was Sun's strategy, not Next's.
WebObjects was fundamentally just a bad abstraction, so good thing too.
Hey PJ, I like your posts because you have the historical background on a lot of this stuff that industry has mostly forgotten.
But... Since you mentioned it, I actually have read J2EE and WebObjects documentation. And I conclude that WebObjects was shit. It drew the 'Web MVC' line at the completely wrong place. Nobody ever cared about about DOEs or whatever, they just wanted a database driver. You look at this huge pile of industry crap and its no wonder why Rails was successful.
I can believe that, but I recall some tradepress article about more than 100 companies selling non-java 'web middleware' who got bowled over by J2EE, and otherwise Next would have just been another one of those. That was Sun's strategy, not Next's.
WebObjects was fundamentally just a bad abstraction, so good thing too.
Here, https://en.wikipedia.org/wiki/Distributed_Objects_Everywhere
If you know J2EE 1.0 and read the WebObjects for Java documentation, there will be very similar examples.
Hey PJ, I like your posts because you have the historical background on a lot of this stuff that industry has mostly forgotten.
But... Since you mentioned it, I actually have read J2EE and WebObjects documentation. And I conclude that WebObjects was shit. It drew the 'Web MVC' line at the completely wrong place. Nobody ever cared about about DOEs or whatever, they just wanted a database driver. You look at this huge pile of industry crap and its no wonder why Rails was successful.
1 reply →