in reply to
Re^9: a few clarifications
in thread Win32 Hosting companies not supporting Perl
Oh, please, the histrionics aren't amusing any more.
Nor is your blindness. Because of a few pages you've found on the net it 'looks
' like microsoft has provided a solution. For which version of IIS is that? Could you be refering to the very CGITimeOut feature I mention in my first post? Did you know that different flavours of windows come with different flavors of IIS even if they are the same version? Could you actually have no experience with this? With your countless inaccurate comments it appears so. Why comment on something you are clearly unaware of. You put me on the spot to come up with a solution, then ridicule the answer. The alarm process is clearly part of the soluton, and there are ways around it being broken. I'm working on them now for my XS perl module. I'm Actually
up to my arms in perl guts right now, working on a solution to this problem. Not blaming everything else while win32 hosting companies abandon perl in droves.
There are some of quick comments from people who don't understand the problem, there is always someone willing to tell you how great perl is and that it's s**t doesn't stink in a perl community, it's not hard to find. I never stated this is a perl problem, I never said it was a bug in the perl code. That doesn't mean perl shouldn't be able to deal with it. Then there are some genuine comments from people who have expereinced this problem on win32 in the real world. Like all the people that pm me telling me I'm fighting for a just cause.
It's possible that I have no clue here how webservers work, haven't been up to my elbows in perl 5's guts on several platforms, haven't been working on perl 6, and aren't the guy who'd have to design the bits that'd be needed to make something like this work in the future.
You clearly don't have a clue. There are posts here that agree with me, there is a real life post of a Win32 perl developer that knows the problem, and low and behold they are changing to a different language BECAUSE OF THIS PROBLEM. Just as hundreds of hosts and companies are doing, and it's people like you that are making it happen and will be the death of perl!
I'm not going to post to this thread any more. Your backward opinion is known and so is my Perl loving view. Luckily the majority of perl contributors I've contacted are telling me it's a good idea, and I have a lot more respect for their opinions than yours.
Working to make Perl the most popular scripting language on the net
- against any that would stop it