On Thu, 9 Sep 2010 14:27:48 -0400
David Nolen <dnolen.li...@gmail.com> wrote:
> On Thu, Sep 9, 2010 at 2:17 PM, Mike Meyer <
> mwm-keyword-googlegroups.620...@mired.org> wrote:
> > > run the risk of fubaring some or all of the previous applications.
> > That problem exists no matter how you do the configuration. But the
> > less per-application configuration you have to do, the less likely it
> > is to happen.
> Also note that you have a certain bias as some us do based on prior
> experience. I for one do not like Apache at all and will not shed a tear if
> I never use it again for my own projects. I'd never use bash shell scripting
> for anything beyond my .profile, much less writing a web app.
Which is why I started with "I can do it with 0 configuration with my
favorite tools installed, how close can javaland tools come to that?"
It wasn't until someone asked me to demonstrate that apache and sh
(god save us from bash) entered into it.
Of course, the choice of apache and sh is irrelevant. I could have
used pretty much any Unix web server, and pretty much any programming
language which plays well in that environment, with about as much
effort. There might have been some trivial changes to adopt things to
some of them (compiled vs. interpreted, .cgi suffix vs cgi-bin
directory, etc.), but the point remains that the underlying philosophy
of this ecosystem means that simple things are simple.
> Note, that if I don't know anything about apache or bash, then you have no
> valid point. There is nothing simple about installing apache from scratch.
> There's nothing simple about bash shell scripting. On *some* systems getting
> these installed is easier, on other systems it's harder. Depending on which
> tools/languages/databases (and, god forbid, which versions) I'd rather use,
> it can be much, much, much harder.
Which is why I *explicitly* asked people to show me how to do this
using *their favorite tools*.
> So enough about simplicity. What we're really talking about here is
> familiarity. It's takes me no time at all to get a working Clojure web app
> and running. I have no idea to do the things that you are describing as
> being simple with apache, httpd.conf, and bash.
No, it's not about familiarity, it's about boilerplate. You provided
an example that was much better than anything I expected to find. I'd
still like to see what it takes to use that to create something I can
deploy on Tomcat or GlassFish or whatever, than as a standalone
server. Having to run standalone servers for every little applcation -
isn't simple
<mike
--
Mike Meyer <m...@mired.org> http://www.mired.org/consulting.html
Independent Network/Unix/Perforce consultant, email for more information.
O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
