12 Reasons not to use MS on your next web project

Posted Monday, November 07, 2005 11:06 PM by Mischa Kroon
On Mr Scoble's weblog there is a list of 12 reasons not to use MS software for your new web project.
Which of the folowing reasons would you experience as genuine reasons not to use the MS platform:

1) Startup costs. Linux is free. Ruby on Rails is free. MySQL is free.
2) Performance per dollar. They perceive that a Linux server running Apache has more performance than IIS running .NET.
3) Finding tech staff is easier. There are a whole new raft of young, highly skilled people willing to work long hours at startups who can build sites using Ruby on Rails.
4) Perception of scalability. The geeks who run these new businesses perceive that they can scale up their data centers with Linux and not with Windows (the old “Google runs on Linux” argument).
5) That Microsoft doesn’t care about small businesses. After all, Microsoft is an evil borg, but Ruby on Rails comes from a single guy: David Heinemeier Hansson. He has a blog and answers questions fast.
6) That open source makes it easier to fix problems and/or build custom solutions. A variant of the old “Google or Amazon couldn’t be built on Windows” argument.
7) On clients, they want to choose the highest-reach platforms. That doesn’t mean a Windows app. Or even an app that runs only in IE. It must run on every variant of Linux and Macintosh too.
8) They don’t want to take shit from their friends (or, even, their Venture Capitalist). Most of this is just pure cost-control. I can hear the conversation now: “OK, you wanna go with Windows as your platform, but is the extra feature worth the licensing fees for Windows?”
9) No lockin. These new businesses don’t want to be locked into a specific vendor’s problems, er products. Why? Because that way they can’t shop for the best price among tools (or move to something else if the architecture changes).
10) More security. The new businesses perceive Linux, Apache, Firefox, and other open source stuff to have higher security than stuff built on Windows.
11) More agility. I’ve had entrepreneurs tell me they need to be able to buy a server and have it totally up and running in less than 30 minutes and that they say that Linux is better at that.
12) The working set is smaller. Because Linux can be stripped down, the entrepreneurs are telling me that they can make their server-side stuff run faster and with less memory usage.


Comments

# re: 12 Reasons not to use MS on your next web project

Tuesday, November 08, 2005 10:51 AM by Nathan Pledger

Start up costs are a key reason, but as you have to pay for your hosting in some way anyway (whether you host it yourself or not) you might as well forget that argument. Unless of course, you have existing skills in those areas. At the end of the day, the real cost is the product of time and skill.

The open source argument, to me, means more unstable, untested, unmanaged code projects destabilising my work.

But to be honest, the rest sound like good arguments.

# re: 12 Reasons not to use MS on your next web project

Wednesday, November 09, 2005 2:56 PM by Mike Blaak

None of them:
1. When you buy Windows you got a webserver
And the .NET Framework (which also contains the C#/VB.NET compilers are free to download
2. I've seen other graphs 'bout that...
3. Yes, those PHP-script kiddies with their garagebox software writing methodologies...we have enough software crap around
4. Yeah...perceptions. It's just what you believe instead of you measure
5. Bill's great dream still is: MS software on every computer; so don't get fooled
6. Yes, and then have to recompile all your OS; where did I leave that source DVD? Oh well, I just gonna download the whole crap again and try to get those buildscripts running again...in a couple of months
7. Didn't we speak about web-apps? As far a I know they're just a bunch of HTML/CSS in a browser...
8. ? Who are 'they'
9. Yawn. As if companies like to change their architecture once a week. Think before you buy/build. Second, you can do multiplatform stuff. I believe web-services also work in the UNIX/Linux/Java world.
10. Security principles are something that EACH developer of software should understand and practice. It's not about choosing a platform and never think about them yourself (and hoping that you're safe forever...)
11. Yeah, but what do you run then on that server? vi?. Most hardware already contains preconfigured Windows OS'ses, and I you don't like that, Win2003 Server installs in about 40 minutes (presuming you know what you're doing...but hey isn't that your job?)
12. Ever tried to build a Linux system from scratch? I did, it took me a few months in my evening hours to get a building environment, sources, determine which tools/apps I needed, changing buildscripts because the fail, reading stuff on the Internet etc... Other problems are: not every opensource product will compile or run its latest version under your kernel and development toolchain. So you might have to use earlier versions that contain bugs...need I say more? Last but not least: there is something called Windows Embedded to get a small footprint MS-OS
And then: a few GB of memory is maybe cheaper and faster to get than a bunch of IT-pros/developers to fix things

Leave a Comment

(required) 
(required) 
(optional)
(required)