The constant joke about the Microsoft Web Development Technology Summit was that they were spiking the Kool-Aid® with mind control drugs. There is direct evidence to the contrary:
There was no Kool-Aid®
The drugs were in the bacon
They were Beggin'® Strips
I love bacon
Microsoft is totally amazing and great for open source and doesn't have anything to prove to anyone so why would they use mind control anyway? Yay Microsoft!
With that bit of sass out of the way, I'll get to the meat of the issue: apparently Microsoft finally supports a fastcgi implementation for IIS. PHP via ISAPI has issues (thread safety? stability?). PHP via regular cgi has other issues (loading the entire PHP stack with every request?), but now you can finally run PHP at a decent rate on your IIS server. This is all predicated on the notion that you have access to an IIS server. Then again, if you don't, you can pluck one from the bounty of the internet via a buffer overflow exploit
Yes, I love jokes from 2001
.
Perhaps it's unfair to take potshots at Microsoft. Anything that they can do to open up their software to interoperation is a good thing. If I could do web development on my desktop machine with really good native Windows apps I would rejoice, because I like the interface. However, that's about the only thing that I like about Windows: the crude and sometimes brutal interface. I like the bleak squareness of Win2k, it's the Eastern Europe of operating systems.
Why would anyone choose IIS? That's a tougher question to answer. I've worked in a pile of computing environments: mainframes, windows, and various flavors of *NIX. Until this job at the University, I wasn't writing software -- I was trapped in userland doing actual work. There I had no choice -- I just had to screen scrape, write VBA, or sneak little perl scripts in to hammer data into compliance.
Therein lies my prejudice: I want to be able to sneak in those perl scripts, and I don't want to have to rewrite them for each place that I use them. I don't want to deal with things like the registry, which requires extra tools to back up.
sudo scp -r /etc user@newbox:/oldbox/
The registry is a great idea, but it represents the Microsoft Way: buy in completely to our philosophy or get bent. They finally wrote a new shell for Windows (the Powershell), which sounds completely cool and interesting, but isn't what I wanted: a native bash. I have cygwin, but if I want a shell, I ssh to my linux box. On second thought, I don't have cygwin, because when I built a new computer I figured that it would be easier to reinstall Windows on a new drive than figure out how to make Old Windows talk to New Hardware.
Maybe that's more complicated than it needs to be, and maybe it is not complicated enough. All I know is that I completely understand the urge to stand on the roof and scream in Swedish "Microsoftjävlar
Yes, I love incomprehensibly paraphrasing Danish miniserieses. Did you see Riget? h0bbel said that "jævler" is the Norwegian equivalent of the Swedish word "jävlar."
!"
Nonetheless, I envy Visual Studio, and my experiences with MSSQL Server were outstanding. I even enjoyed the heck out of Microsoft Access (when not using it as a database engine, but rather a front end to MSSQL Server). I understand that ActiveDirectory is pretty cool. Once you buy in to one of these technologies, it can be easier to just buy the next piece that already knows how to talk to your first piece than to build some sort of fragile and magical connector. You've already got a box running IIS that handles some custom .NET app that fulfills your business requirements and want to extend it to handle a bit of PHP on the side? Now you can do so with a clear conscience.
I dunno, fastcgi seems kind of a non-announcement. How about letting me maximize my shell window, mount an NFS drive, read and write my ext3 or murderfs
reiserfs
drive, or have normal line endings
Yes, I know about DOS2UNIX. I have had to write my own DOS2UNIX script because I couldn't find one for the box I was on -- but shouldn't we stop the problem at its source?
.
