Jordan Schatz wrote at 12/19/2011 01:04 PM:
Also it would be really nice to be told how one "should" develop with racket... there is abunch of extra information that could be hidden in an introduction to racket for experienced develops type of manual, and alot of direction that could be given. Probably not even cover that there are stateful servlets, and just say to use stateless ones, include how to use a data store (db, mongo, whatever) and don't cover serializing to disk. Suggest a directory layout and a way to organize servlets, view, model, and controller code. Or if MVC isn't the suggested pattern, make some other pattern explicit.
I suggest that such a tutorial -- which presents a dumbed-down Racket in terms utterly familiar to any Java/Python/PHP/Ruby/etc. Web grunt -- start by trying to scare away any readers who are only looking for a slightly better Ruby.
There *are* reasons to use Racket over almost anything else, but they are things like syntactic extension, dynamic language features, continuation-based Web serving, and the smarter developer community.
Without scaring away readers (or a preface of motivation), there is an implied "Here is YET ANOTHER slightly different syntax for grunting and pushing out Web apps in the exact same way you have been for years, but with a nebulous aura of being somehow better, in some way to be revealed later (perhaps involving artificial intelligence, because, hey, Lisp)."
-- http://www.neilvandyke.org/ _________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/users
