July 21, 2003
@ 04:02 PM

Munich and Linux

My "3 TechEds this year" drinking and partying buddy Stephen Forte says:

Ich Bein Ein Aushlander 

I love the city of Munich (Sorry Clemens, I know you don’t like that part of Germany). I go there usually twice a year. My good friend Nicole and her awesome hubby Chris live there. Being the History Major, etc I love the history all over Munich, even though it is bad history since the Hofbrahaus was the scene of one of the most important events leading up to Nazism and World War II.

I love the UBhan and SBhan. I love the surfer chicks (I can't resist them!!). I love the proximity to the Alps. Five hours by train to Venice. I love the 1/2 beer 1/2 Lemonade drink in the beer garden. Ok, I will stop now on how cool it is there.

First of all, it's not that I don't like that part of Germany. I just like it much more up here in and around Düsseldorf. We've got awesome microbrews (and we mix with Coke and call it "Krefelder"), the Rhein-Ruhr metropolitan area with some 10 million people gives you always something to do, we really know how to party, we've got plenty of U- and S-Bahn too, it's a 1 hour flight to virtually anywhere in west-central Europe, Amsterdam, Brussels, Luxemburg, Frankfurt are less than 2 hours away to drive and you can get to Hamburg in 4 and Paris in 5 hours. ... Ok I will stop now on cool it is here. ;) 

Anyways, Stephen thinks Munich made a bad call by choosing Linux. I think that if they really intend to use VMWare to run their "Windows legacy" they're in multi-trouble.

My understanding is that they felt they were forced to make a choice because NT 4.0 support runs out. So now they're going to run the unsupported NT 4.0 inside VMWare (which does require a license) on top of an IBM/Suse supported Linux? Also, how is it that Linux runs at 30 million Euros (by current estimate) for migration while Windows licensing and support would have been around 27 million before some considerable discounts that MS was willing to give? So here we have IBM and Suse raking in the money for a development and support contract in which existing in-production software is likely going to be entirely rewritten just because it needs to run on a different OS because of "strategy" (which, to me, is complete idiocy) and for support contracts that seem to be, looking at the big numbers, way above and beyond what Microsoft is asking (because IBM and Suse outsource quite a bit of the software development to the community "for free" and look better on the cost side for "licenses").

My experience tells me that that sort of "we force an OS down your throat" strategy fails in any larger company after only a short while and it will fail in government as well. If a departments finds a good software solution for their needs that fulfills most of their business requirements for a fair price, the wallet always wins, and should win, over the geeks in the end. At the end of the day, an OS is what it is: just an operating system. If you have a solution that does what you need for you business you just shouldn't care too much about the OS. If a department uses a "non-strategic" platform and your data-center refuses to give them support, the IT people not doing their job. The business folks make the money for IT to be get their salaries paid. What "strategy" results in way too often is a more horrible and less coordinated zoo of heterogeneous systems than if there were no set strategy, at all. I know of (multiple) banks where mission critical servers run under someone's office desk, because they happen to run the wrong database package or a non-strategic OS and therefore the data-center rejects taking them. Maximum stupidity with a great excuse ("strategy!"). 

On the other side of the fence, if your role is building solutions you should look for the OS and development platform that gives you maximum productivity for writing apps in order to deliver in time and in budget. Being religious about these things is stupid. I know Windows much better than Linux and therefore I am by several magnitudes quicker writing apps on Windows. "You gravitate to what you know" and there's nothing wrong about that.

To me, the Munich & Linux story this isn't a win for Linux in the first place. To me that's a clever IBM coup around "strategy" resulting in way too much German taxpayer money (and 30 million won't do it) being thrown at the biggest computer company (US-based) in the world instead of the biggest software company (US-based) in the world.  How exactly does that amount to a great win in terms of German taxpayer ROI or freedom?

Also, as far as "taxpayer ROI" goes, it should be considered that most German software companies with a working business model (means: make money by having actual customers) aren't into open source. And my best guess is that there is no "yet" there.

Tuesday, July 22, 2003 4:38:48 AM UTC
You are insane. You have absolutely no idea what "beer" means and what it actually *is*. You do not have beer "up" there - and really nobody in the world who mixes beer and cola may claim to say anything about beer, anyway.

:-) .. you know ... ;-)
Tuesday, July 22, 2003 5:16:44 AM UTC
Next time you'll be "up" here, we'll do a lengthy and very educational session with you -- location: Altstadt Düsseldorf.
Tuesday, July 22, 2003 12:41:30 PM UTC
Cool - looking forward to this. Prost!
BTW: the 'Remeber Me' feature for comments does not work for me.
Wednesday, July 23, 2003 1:15:55 AM UTC
Sorry Clemens, I have to agree with Christian on this one! But I'll come to the North and South to party with both of you!
Wednesday, July 23, 2003 5:10:29 AM UTC
Hey Clemens

do you prefer "Alt"-beer?
Daniel Fisher
Wednesday, July 23, 2003 2:56:39 PM UTC
Hi Clemens,
I have 3 things to say about this:
- Linux will pay in the end. In 5 years they won't have to spend again an insane amount of money just because some company decides to stop supporting their software.
- As I believe most of the budget for Linux is dedicated to the training of users. This is interesting, because for the users the step to Linux is as big as from NT to W2K. Just some minor differences in the GUI.
- All the admins will be happy if they get around how to do things with Linux. Having administered a zoo of Windows Clients myself, I can say, this is a very frustrating job. It took me twice as much time to administer the 10 Clients, as to administer as 12 Linux servers. Including setting up a cluster,...

BTW: I don't hate Linux (I'm using it in the moment). I'm also software developer, as this I have to say it's not better or worse to develop with Linux. It's different. You don't have as many agents and visual tools as with a typical Windows IDE, but most often you have a better way to automate things. And a greater array of tools to choose from.

Ciao

Oli
Oliver Denzel
Wednesday, July 23, 2003 10:26:05 PM UTC
Oli,

they will have to pay IBM and SuSe continuously for support and the support cost is going to be as substantial as the upgrade cost for Windows once they upgrade machines to a new, tested version of Linux once they decide to do so.

The biggest problem with Linux is that it is too much in flux. If you have proper quality management in place, you will have to essentially freeze the deployment on a very well defined version. Then you will have to maintain that very well defined version. Throwing in new versions of components isn't an option here. If you have a security vulnerability or a showstopper bug for version 2.1.3.1 of some component, you need to get a patch for that version. That's the difficult part, because very often that means that you need to retrofit the patches into your version yourself, since the common gospel in the Linux space seems to be "get the new version".

* I wouldn't underestimate the training effort and the barriers that need to be overcome. If you go from NT to W2K, the end user experience does change, but it doesn't change as radically as with Linux. "Ordinary people" invest heavily (with private time and private money) in their own education and they are happy with the way they can navigate around in their favorite word processor - if you force them to switch you annihilate quite a bit of that. That adds to frustration and makes them less productive.

* The administration side is very much a thing of using the right tools. Windows clients can be zero-touch if you bolt down the policies ans security settings and automate patch management.

I won't argue about the developer tools issue, because that is, as I said, a matter of taste. My development environment is as automated as I need to have it and I am not missing any tools -- on Windows.

Cheers,
Clemens

Thursday, July 24, 2003 7:35:46 PM UTC
Hi Clemens,

you wrote: Windows clients can be zero-touch if you bolt down the policies ans security settings and automate patch management.

Not true in Munich: (see "Kurzfassung der Clientstudie LHM", p. 23):
"Munich ... neither uses Microsoft Back-Office products on their servers or for system administration ... With regards to system administration this tends to favour the use of Linux for the clients."

So, the dice had been loaded right from the start. I.e. it's very easy to invent some fancy restrictions (no Windows servers allowed) in order to get to the conclusion that the use of IBM/Linux was the best option and money or migration risks wouldn't matter.

Microsoft is at risk of losign their entire server (and as a result potentially: client) business in Germany due to recent recommendations from the "Koordinierungs- und Beratungsstelle für Informationstechnik in der Bundesverwaltung im Bundesministerium des Innern":
http://www.kbst.bund.de/SAGA

They're mandating the use of J2EE (.NET has been relegated to a status of being "under observation" and classified as being not in compliance with the mandated "OS indepence" -- not hard to guess why they elevated the importance of this criterion to keep MS out ...).

CU,

Moritz
Moritz Berger
Comments are closed.