> Ok, fine with me! But, if you want to tell this to your potential users, > you must also give them a reason to switch. If the reason to switch > is not to use TCL and use the AOLserver API, what is it? Users won't > switch because they can leverage the vast knowledge they already have, > for the simple reason they can already do that on Apache.
Oh, there are a lot of people out there that will give AOLserver a try if only they are able to use it with something they need anyway, let's assume PHP for the sake of that thread. I talk about curiousity, giving something a try, learning and understanding something, 'being different', -- if it works as stable as with Apache, why use Apache? Please don't get me wrong: I don't want to insist on the PHP-train, but I think this big-budget-decision-thinking and rational-arguing-thing is strategically wrong. There are more reasons than superiority, best-of-breed, premium, world-class, amazing - bla bla bla bla - features for people to prefer one thing over the other. Things evolve. Remember how unthinkable BAD PHP was in it's old days? Today you can talk about it and and win the competition, because the little son of your potential customer runs the family homepage with it. In the meantime we * pay more for webspace, because our server is unknown (not good for people who want to give it a try) * are confronted with 'Tcl - what?' questions (not sexy for people who want to give it a try) * have _two_ arguments: '...backbone of the largest and busiest...' and '...for large scale, dynamic...' (not enough for people that google hours for finding out how to do virtual hosting) I'm not arguing for implementing PHP to change that. I simply hope that the Community plays a bigger role in the future of AOLserver and it's features. > So, what advantage does it then have to run PHP (or language x) on > AOLserver instead of Apache? This a critical in the communication to potential > users, since, likely they already use Apache. One advantage is that an AOLserver administrator, confronted with the requirement to offer PHP (for WHATEVER reason), would simply add PHP to AOLserver with no need to install Apache. Because it's AOLserver he/she is competent in, not Apache. This scenario is the opposite of yours, where the person already likes and runs AOLserver and does not have to be convinced. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
