We've been talking on IRC about this.
I actually think that we don't need a command line tool for the Web server.
One of the major thing I've tried to do since I've maintained the Web
server is to make it more configurable and in particular make the
configuration happen in the language (in good PLT style.)
The command line tool is in opposition to that goal, so it's been left
in stasis since I've worked on more configuration.
It has gotten to the point where the command line tool is basically
useless and I don't think many users actually use it.
As far as "name" goes, I like the idea of the Web server being known
as "the Web server that is part of Racket" or "Racket Web Server" is
papers OR "the Web server made by those PLT guys" or "PLT Web Server"
(still) rather than something "cool." I've tried to uniformly write
"PLT Web Server" in papers/etc rather than "PLT Scheme Web Server" to
encourage the second interpretation.
Jay
On Tue, Apr 20, 2010 at 6:49 AM, Jay McCarthy <jay.mccarthy at gmail.com> wrote:
> I like the unity of a single command for REPL and everything else. I
> also like Robby's idea of turning the complex mzscheme syntax into
> some sub-commands, although I don't know how that will be done. I'm a
> bit sad to see rico go, but that's fine. I'll probably alias it.
>> As far as the Web server's name... I agree that 'racket-web-server' is
> awkward. Changing the name to something else other than "PLT Web
> Server" will be weird. In the world, it is horribly branded, people
> write "Continue Web Server", "PLT Scheme's Web Server", "PLT Scheme",
> "PLT Scheme Web Server", and endless permutations.
>> If we went the way of changing the name to something more Web 2.0
> sounding, like a Native American tribe or some spider-based
> pun/cleverness; then I think that suggests making a totally separate
> command. "racket chippewa" is a lot different than "racket compile"
> [1]. If there is a name change, I don't feel comfortable choosing it
> just because I'm the current Web server maintainer, I'd rather to the
> traditional voting, etc.
>> Leaving it as a sub-command:
>> racket web-server
> racket web
> racket servlet
> racket serve
> racket http
>> This emphasizes its job rather than its "name".
>> Jay
>> 1. As an aside, should "racket planet" be "racket package"? Or "racket
> packet"? :P
>> On Tue, Apr 20, 2010 at 5:52 AM, Sam Tobin-Hochstadt <samth at ccs.neu.edu> wrote:
>> On Tue, Apr 20, 2010 at 3:27 AM, Matthew Flatt <mflatt at cs.utah.edu> wrote:
>>> My preference is still to turn `plt-web-server' into `racket
>>> web-server', because the point of starting the web server is ultimately
>>> to run some Racket code that you wrote. (Along the same lines, I think
>>> it makes sense to add `scribble' and `slideshow' commands.) Giving the
>>> web server some non-generic name seems ok, too. Changing
>>> `plt-web-server' to `racket-web-server' seems awkward to me, because it
>>> would be the only important command that starts `racket' but uses a
>>> hyphen instead of a space.
>>>> I agree on the badness of 'racket-web-server', but I still don't like
>> the idea of making the web server into a subcommand. Therefore, here
>> are some suggestions for web server names, following the Native
>> American tribe name tradition [0]
>>>> - Ute or Shoshone, tribes from Utah [1,2]
>> - Chippewa, a tribe with a game called "Ball and Racket" [3]
>>>> [0] Apache, Cherokee
>> [1] http://en.wikipedia.org/wiki/Shoshone>> [2] http://en.wikipedia.org/wiki/Ute>> [3] http://www.apples4theteacher.com/native-american/games/ball/ball-and-racket.html>> --
>> sam th
>>samth at ccs.neu.edu>>>>>> --
> Jay McCarthy <jay at cs.byu.edu>
> Assistant Professor / Brigham Young University
>http://teammccarthy.org/jay>> "The glory of God is Intelligence" - D&C 93
>
--
Jay McCarthy <jay at cs.byu.edu>
Assistant Professor / Brigham Young University
http://teammccarthy.org/jay
"The glory of God is Intelligence" - D&C 93