Stability problems with ASP / .NET
People always try to tell me that IIS / ASP / ASP.NET is just as stable as Apache / PHP.
The Canada Post website has been down for hours, simply displaying:
A ScriptEngine threw expection ‘C0000005′ in ‘IActiveScriptParse::ParseScriptText()’ from ‘CActiveScriptEngine::AddScriptlet()’.
I know C0000005 errors well from my Win32 C++ programming. It’s a generic “access violation” or crash error. It means something is seriously wrong.
Now, you can tell me, “They haven’t applied patch X”, or, “They haven’t configured Y properly”, but I see this sort of thing all over the net. Even Microsoft’s own pages have these errors from time to time.
On the other hand, I rarely see PHP error messages. Even when I do, they’re typically “can’t connect to database” timeouts on an overloaded server, as opposed to major system crashes like the message above.
I continue to assert that Apache/PHP is generally more stable than IIS/ASP.
April 4th, 2007 at 1:59 pm
Well I don’t think errors or lack of them displaying on websites is any proof of stability of the environment. I mean, you can have crappy-ass development done on any environment. Errors on a website are more about the abilities of the developer in working with that particular environment, than anything else.
April 4th, 2007 at 2:20 pm
That’s a really good point, but I still see a lot more IIS/ASP errors than Apache/PHP, even though Apache is the market leader.
I’m pretty much assuming it has something to do with the technology, as opposed to the skill of the developers in either camp.