Titi Ala'ilima wrote:
Gleaning from this conversation a few main points/questions, with a couple
cents of my own thrown in:
1) AOLserver probably needs a new name. Something that uses the NS initials
would be ideal so that all those ns_* commands actually make sense again.
Could we resurrect the NaviServer name?
How about The NuffSaid server. Why should you use it? It's good. It's
got Tcl. 'Nuff said.
Sorry I read a lot of Marvel comics in the day.
2) The biggest bang for our buck would be improving the Tcl language and the
codebase available for it rather than bringing in another popular language. It
took Rails to put Ruby on the map. What would our Rails be?
I would be careful to say "improve upon, or enchance the Tcl libraries"
rather than the language.
3) What other features does AOLserver lack that would tap into current trends, or
possibly create future ones? Server-side JS is interesting, "Comet" support
seems like a good candidate?
4) Who could sponsor AOLserver development apart from AOL? Does anyone know of
anyone with a large deployment of AOLserver?
I think it would take no more than some web space and, at best,
subsidizing a full-time developer or three.
5) Which will come first, Tcl gaining in popularity or AOLserver, or do they
both need to grow together?
6) If AOLserver remains a targeted product, as it seems right now it should,
it's usefulness will be limited by what can run on it, and what can integrate
well with it. Which is fine, but we need to have that clear in our minds as we
proceed. I don't think we want to topple Apache per se. We want AOLserver to
carve out its own path, and if along the way it makes Apache, etc. irrelevant
then great!
Each tool has its own strengths, and you should play to those
strengths. When you try to be everything to everyone you end up being
some things to some people and loved by no one. Look at Microsoft's
"edlin 2007" with built in Javascript and VB-scripting, hooks into Win32
and the driver layer and a 37MB run-time on top of .NET 3.0. Oh, and it
requires Monad, VS2007 and to be installed on Vista Server for full
functionality. It doesn't have full-screen editing, but you can use it
write a virus in 17 lines of code.
Like you said: Don't approach AOLServer as something to make people
want to chuck Apache. First make it something to attract new users for
new projects... if it does that good enough, it will start to replace
Apache on its own.
-Titi
--
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.
--
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.
