Is There a Need for a GNU Lobby?

Anonymous Coward writes "Data Warehousing is a field in which you dump data from a lot of different databases, transforming it in some way and load it in a new, business-oriented database. Somewhere along the way, you need to transform a HUGE load of data, and there are VERY expensive copyrighted tools that 'help' you do so. While working on a job for a client, we developed all of the transformation process using GNU tools (SunOS 5.6 and a nice E10K machine, if you want to know!) and found out that it was MUCH faster and even cleaner than with the particular transformation tool that we were 'supposed' to use. Our client (a big bank...) went berserk and started talking about 'lack of support', especially since the management had already bought the other tool and paid $200K for it, so they didn't want to look stupid. What they did was pay for the redevelopment using their transformation tool, only to find out in the the end that the process was taking 20 hours longer (approx 5x increase!) Now that we are going back to the original solution, I am thinking about what arguments I could have used 6 months ago(!) to prevent this? Maybe there is a market out there for consulting companies that offer GNU/Linux support and can reassure the management about these solutions?"

Comments

I don't get it

[PD]

You want a gnu in the lobby? What's wrong with the parking lot?

Why cant you support it?

[bellings]

Ok... I don't understand this at all. One of your clients only wants to use supported tools and is willing to pay tens or even hundres of thousands of dollars for support. At the same time, you have a fast, flexible solution that works, you have all the source code for that solution, you have every legal right to use and modify the source code for that solution, and you have the knowledge and ability to maintain that solution.

So why are you asking us what to do? The answer is simple -- sell your clients a support contract, and support the tools yourself. You have the source code -- what the hell do you think it's for?

I think you answered your own question.

[Pogue Mahone]

Our client (a big bank...) went berserk and started talking about 'lack of support', especially since the management had already bought the other tool and paid $200K for it, so they didn't want to look stupid.

Here's the answer, you provided it yourself. They spent a lot of money on the tool and didn't want it to look like a complete waste of money to their PHBs - so they insisted that you used the expensive tools.

However, after discovering that the expensive tools really were a crock'o'shit, they decided to cut their losses and save on the (no doubt equally expensive) upgrade/maintenance treadmill.

Unfortunately, it actually takes a complete disaster before people with this kind of mindset will come to their senses - and sometimes even a disaster doesn't work. How many people do you know that expect the next version of [insert pet hate here] will somehow fix all their problems with the current version, despite the fact that all the previous versions haven't shown any likelihood of doing so? This is just the same optimism, but on a corporate scale.

--

How did they know?

[ryants]

I'm interested in knowing, How did the suits find out?

Anyway, more to the point, support for GNU stuff already exists to a limited extent. You can buy support from Cygnus for gcc/gdb. You can buy support from RedHat for their distros and most of the stuff included therein. Cyclic supports CVS.

And I'm sure there are numerous little startups out there that I don't know about that are getting into this... or maybe they don't exist, and there's a business opportunity for ya.

Ryan T. Sammartino