WIMP or WAMP?

For the past few years I have been running some software on a WIMP stack. They have been working quite well. I never had any issues with the technology stack itself. Or rather the only issues I had at times stemmed from the fact that a lot of PHP apps automatically assume that you are running Apache. So lately I had this crazy idea to try switching things around and running things on top of a WAMP stack. Here the thing though…

Long, long time ago, in a galaxy far, far away - as as I call it “back in college” I participated in a discussion on this very topic. It started with the following statement:

“… and on top of that they are running Apache on windows which is kinda stupid!”

This was met with round of nods, and approving grunts from everyone. Since I was the youngest, dumbest and least informed person in the room, I nodded too. Then asked why was it stupid, trying to figure out whether or not I should immediately uninstall apache from my home desktop.

The answer I got was sort of convincing. Apache was never designed to be run on windows. It was ported back to windows - it works because of kludges and hacks were made. It will never be as efficient as a server designed from ground up for the platform. It won’t scale and etc.. This was followed by another round of nods. One again, since I was least experienced, and least knowledgeable person there I didn’t argue the point and taken it as a given. From that point I always tried to run pure LAMP when possible, and if I had to use windows then use WIMP instead of WAMP. And of course I always figured:

“I have this windows box here, and it comes with it’s own built in server, so why would I install another one on top of it”.

Now that I think about it, I can’t really find any empirical data - any tests, or benchmarks which would support the convincing IIS vs Apache argument from my distant past. There are millions of various arguments on which one is better out there but most of them boil down to “Apache is better because it is open sauce” or “IIS sux because it is from Micro$not” and so on. Serverwatch has a nice, objective cross comparison between the two - and if you look at it, you will see that both are almost equivalent when it boils down to features. IIS is better at running ASP, and integrating Windows specific stuff. Apache on the other hand is multi platform and integrates better with linux-y technologies.

I really believe that the whole “Apache is a port” logic is faulty. It is an open source project after all, and people have been successfully deploying it on Windows for years, even in production environments. I’m sure it grew up considerably in the last 6 years or so since I had that conversation too. So if it was flaky back then, I’m sure it is not flaky now.

What do you think? Is WAMP a viable option these days? Should people stick to WIMP? Or is WIMP the abomination here? Is PHP really better off pairing up with Apache? I’m throwing it out there because I honestly don’t know. On one hand, I don’t want to try to fix what is obviously not broken. On the other hand, perhaps running WAMP would be more beneficial in a long run. LAMP is not really an option at that location I’m afraid.

Related Posts:

  • AJAX and me
  • The specified CGI application misbehaved
  • DST Readines Test for MySQL and PHP
  • Project Idea
  • What kind of applications do you have open right now?
  • How to talk to users?

  • 6 Responses to “WIMP or WAMP?”

    1. Gravatar Nathan UNITED STATES Says: Reply to this comment

      I’ve run a low-volume WAP (no database) server for years. Maybe the discussions were valid at one point, but Apache 2 seems to be pretty darn Windows-friendly.

      I don’t have anything major against IIS, really. I found Apache easier to configure and getting new versions for free appealed to the poor college student I was at the time (yeah Windows comes with a crippled ancient version of IIS (at least, the version that came with Win2k was both ancient and crippled; I don’t know if XPs is any better), but you’ll probably be dropping some dough if you want the most recent, unrestricted version). Plus, don’t underestimate the awesomeness of open sauce )

      Posted using Mozilla Firefox Mozilla Firefox 3.0 on Windows Windows XP
    2. Gravatar Hector SPAIN Says: Reply to this comment

      I agree with Nathan.
      I’ve been running WAMP at a low scale level (with database, but quite small) for several years now, and works fine. No empirical data, sorry.
      My main reason to use WAMP over WIMP, though, is that it’s in fact developed as LAMP application that has to work over XP too, due to some customer requirements. Oh, man, and now I’ll have to check what happens with Vista!
      And of course “IIS sux because it is from Micro$not”. -)

      Posted using Mozilla Firefox Mozilla Firefox 3.0 on Linux Linux
    3. Gravatar Dr. Azrael Tod GERMANY Says: Reply to this comment

      got the same reason like anyone else… its easier to switch between lamp and wamp than to switch between lamp and wimp.
      But on the other hand… i dont do much switching in last time… used lamp most exclusively the last 3-4 years. (besides using Linux exclusively as Desktop OS the last 2 years)

      Posted using Flock Flock 2.0b1 on Linux Linux
    4. Gravatar ido ISRAEL Says: Reply to this comment

      What about WLAP? (L standing for Lighthttpd)
      That’s what all the cool kids are doing now.

      Posted using Mozilla Firefox Mozilla Firefox 3.0.1 on Windows Windows XP
    5. Gravatar ido ISRAEL Says: Reply to this comment

      oops. should be WLMP of course…

      Posted using Mozilla Firefox Mozilla Firefox 3.0.1 on Windows Windows XP
    6. Gravatar Craig Betts UNITED STATES Says: Reply to this comment

      Personally, I choose to run SAMP.

      Long live Solaris!

      Posted using Mozilla Firefox Mozilla Firefox 3.0 on Solaris Solaris

    Leave a Reply

    XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <pre lang=""> <em> <i> <strike> <strong>

    [Quote selected]