Proprietary Legacy doublespeak

You know you’ve been had when a vendor starts telling you to stop using proprietary software, and use their open software instead.

You know you’ve been had when they call your existing working living breathing system a legacy so they can sell you their unproven flash in the pan technology. Not withstanding the fact that you did adopt their previous flash in the pan technology that is now your legacy.

So I knew it was time to throw up when I received an invitation to a webinar from Redhat touting “Now, using Java EE can be even simpler than using proprietary legacy frameworks such as Spring Framework, and take much less time.”

Can’t they see that no one cares about the old open Java vs proprietary software talk anymore. The whole reason for the widespread adoption of Spring was that it just worked. Let me repeat that - it just worked. It’s a product made to serve you the developer. Not a standard made to serve the vendors. All the previous multi-vendor ivory tower J2EE standards were not products. They weren’t usable. You couldn’t read the standards and use them. You had to use a bad product that didn’t care about solving your problems, but about adhering to a straw man standard. Unlike Springframework or even Grails which are usable products, borne out of the need to solve real problems for real developers.

I bet they were just trolling.