Interview with Red Hat's New CEO 129
mjasay writes "Red Hat just got a new CEO, Jim Whitehurst, but based on a recent CNET interview with him, he's cut from the same cloth as Matthew Szulik, Red Hat's former CEO. He won't buy an iPod because it won't play Ogg Vorbis files. He refused other CEO roles because he 'must have a mission.' He suggests that taking proprietary shortcuts is a fundamentally wrong way to build a software business. And he believes Red Hat should be doing $5 billion, not $500 million. It's a question of operational excellence and on focusing on its core businesses, according to Whitehurst."
what player plays ogg files? (Score:3, Interesting)
I like the guy. (Score:3, Interesting)
He says that redhat should be making about 8 times more money than it does now. I agree with him. The spectacular growth linux as a plataform has enjoyed is spread out between many other distros, and thus the next step is convincing some in other linux platform that the redhat value proposition is a better way to go. If I was him, for example, id introduce a discount and some free consulting if you're migrating from competing platforms.
Remember, subscription is a long term bussiness. You dont get your wealth of money until time passes and youre able to amortize the initial costs of getting your distro to the customer and deploying a sales network, so, as a bussiness model, I think redhat and suse can ONLY grow in revenue (I love this FOSS thingie, it will make many of us a decent living doing what we love).
Now, i really know certain stuff that goes on inside redhat (im not directly related to them, but lets say they've been my clients at some point in time). This is a very cost-effective operation, totally commited to increasing revenue in every little single aspect of it. The last CEO was very effective in conveying a corporate philosophy that saves and saves and saves money and resources, and i think it has resulted in supperb products and services, from my POV, the best in the industry; and not in huge salaries for executives and the kind of corporate shit that kills good companies.
I wish the best to redhat with this new guy they have, I think he should be focusing in providing a better and better positioning for the redhat brand in the IT support and services industry; and to leverage the potential of the Red Hat Exchange idea. If they hit it with that one, they'll grow fourfold in less than two years, mark my words.
it still comes down to software. (Score:4, Interesting)
They'd all make a fortune.
And it would give Linux the software it so desperately needs to survive.
RS
Re:what player plays ogg files? (Score:3, Interesting)
Re:Same Old, Same Old (Score:3, Interesting)
I am also sure that they could do really well in a desktop market, if only they wanted to. That would bring a whole hip of complexity to the way Red Hat does business (and development) but I'm now certain that underlying technology is finally in a good shape to start something like this.
core business (Score:3, Interesting)
Re:where does Red Hat need to start? (Score:3, Interesting)
That's a rather debatable statement.
"Apt just plain works better than rpm"
To make a car analogy, that's like saying buses work much better than people.
rpm (the file format) is comparable with
"A year or so ago, RH promised to fix rpm to make it as useful as apt."
Eh, IIRC, they promised to fix rpm. Which had some flaws (of mostly estoteric nature, which usually werent the actual problem users ran into).
The main issue has been getting redhat and fedora tracked into yum, yum improved and the gui tools polished. Personally I think they're on the right track and getting much closer; yum is getting pleasant to use (and dependency handling is getting exemplary if you install and activate yum-priorities and set your repo priorities (I'd really suggest they install and use it by default, it would prevent users shooting themselves in the foot unless they force the issue and increase the prio of a third party repo))
There are still speed issues (altho they've vastly improved recently), but as far as I can tell they're mostly due to erring on the side of caution ensuring that repo updates wont have broken the local picture of the current situation. I can appreciate that.