Thanks for the comment, Johnny, but in the third to last paragraph I do suggest using open source wherever it makes sense; often in commodity situations, but actually wherever it provides you the best functionality to meet the need (“whatever terms and conditions are used”). Functionality rules is my consistent mantra.
The length and complexity of the blog post is due to the length of the Ingres CEO’s two-part 2500-word advertorial and his article’s many misleading assertions. The article:
• conflates SaaS and open source
• pretends that his company is like Red Hat in terms of open source culture bona fides
• asserts that open source software is not licensed
• implies that IBM, Microsoft, Oracle, SAP and other market-leading enterprise software suppliers do not offer SaaS delivery and software licensed under open source terms and conditions
One of the things I try to do on my blog is warn IT folks about the marketing tricks suppliers try to pull (in this case, making an ad seem like a legitimate piece of Fortune editorial content). In my opinion, anyone on IT staffs and in IT management risks the success of his or her mission by following the Ingres CEO's self-serving advice, such as:
• Try to change packaged software into inhouse-developed software
• Save money in their IT budgets on the software line item when the real opportunity is in systems integrators, other outside consultants, etc.
• “Donate your software to non-profits” or whatever he is suggesting in that non-sensical paragraph
• Buy into the “open standards” bulloney philosophy; how many meaningful standards are not really the instantiation of a popular product? (but his advice is worse than that; he is suggesting adopting all so-called open standards)
Thanks again
Dennis Byron
Dennis,
I enjoy reading your postings very much and appreciate your no-nonsense insights. On this particular subject, I do want to put a plug in for Ingress, a company I have much respect and regard for.
Ingres is a strong open source participant, including serving quite actively on the Open Solutions Alliance (OSA) and the Open Source for America (OSfA) non-profit organizations. Much of this work supports non-Ingres products with their shared mission of helping building open solutions and fostering open development. They also sponsor open source academia opportunities and have a strong community from which they openly accept contributions.
They certainly help make my work at the OSA and the OSfA much more rewarding and productive.
Thanks for all your insights, and I look forward to your regular posts.
Best regards,
Anthony Gold
Topic: Enterprise Software Vendors
From operating systems on up, these vendors sell the software that runs large companies
Blog: Four MDM Stumbling Blocks
Article: Viewing OpenWorld With An Open Mind
News: Zettaset Initiative Brings More Access Control to Hadoop
Related Topics
Enterprise Software, SaaS
Red Hat Enterprise Linux: Migrate from Solaris with ConfidenceThis white paper discusses why the Linux platform's flexibility and reliability make enterprise-class Linux systems an ideal choice for your x86-based server migration projects.
VMware View and NetApp Storage: Best Practices for Design, Architecture, Deployment, and ManagementThis solution guide provides guidelines and best practices for architecting, deploying, and managing VMware View (VDI) solutions on NetApp storage systems.

Service-oriented architecture is the catalyst that allows today's companies to respond to business demands faster and more effectively than ever.

Comprehensive storage solutions for better data access and retrieval, leading to better-informed business decisions.

Technology that allows you to sell more, provide better service and significantly improve your bottom line.

Tips, tools, and expert commentary to help you get the most from your company's most valuable asset - its employees.
Dennis, you do a good job of making something simple sound complicated. What is so hard to understand about not paying premium prices for a commodity product by choosing open source? Or use open standards to avoid getting technically locked into a proprietary vendors stack so you have no room to negotiate?