B.K. wrote:
[snip]
> Thirdly, about questions already been asked, well here is
> something to think about. The other day I got a haircut, and I
> asked a few people how it looked since it was a little different
> from my previous haircut. And I got many responses. I actually
> never heard the same answer twice. Everyone whom I asked had
> another critique or comment on my new look. Same thing here, an
> answer to a question was already posted, so what? You ask it
> again, I'm sure you will get new answers not listed in the
> archives to the same question.
The difference is that some things (not haircut opinions) can
actually be answered definitively.
ex.
Where do I put (servlets/tags) using (insert servlet engine of choice)?
Something like this can be answered according to the specs of the mfg.
and there really doesn't need to be any more discussion.
> If you are a Developer and think that there is only one concrete
> way to implement something, then you are in the wrong business
> buddy, no offense of course.
Sometimes there IS:
ex.
" I keep getting an error on my page ... here is my code "
<% int number = "hello world"; %>
--
On the other hand, some things aren't as much factual answers as they
are opinions, and therefore can continue to thrive.
ex.
Which is better, template engines or jsp?
Relative merits of Model 1 vs. Model 2 architecture.
etc.
=====
I think the issue people have with repetitive questions isn't that
they don't want discussion, but it often seems that people post their
question waiting for someone to solve their problem for them instead of
spending even 5 minutes to look it up for themselves.
- vin
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
