2011/12/8 Cédric Beust ♔ <[email protected]>
>
> On Thu, Dec 8, 2011 at 8:20 AM, Josh Berry <[email protected]> wrote:
>
>> I can't help but thinking the "javadoc" style of thinking
>> you can jump in at any given method to fully understand what is
>> happening somewhere is a fallacy that causes more harm than is
>> admitted.
>>
>
> How is that a fallacy? I think it has worked very, very well overall. I
> consult Javadocs several times a day (most of the time from my IDE, which
> is another great progress in documentation browsing) and it does help my
> productivity significantly. Obviously, a Javadoc is only as good as the
> quality of the comment, but by now, Java has some very spectacularly well
> written doc across the board (both the JDK and external libraries such as
> Guice or Guava).
>
> Just this morning, somebody posted on scala-debate a very interesting
> report of his experience getting up to speed on Scala, and here is one of
> his points:
>
> There is definitely a huge price to pay developing Scala code because the
> IDE support is so poor. Writing Java code in Eclipse goes so much easier
> because of all the help the IDE editors give you. The fact that Eclipse
> lets you hover the cursor over things and brings up these great
> semi-persistent tool-tips with hyperlinked javadoc makes productivity
> incredibly high.
>
>
In fairness, it's also worth pointing out that the user in question was
trying to edit standalone script files in a directory that was explicitly
*not* marked as a source directory in the IDE. If it had been, he wouldn't
have lost much of that goodness. The full quote:
*"In my current utilities environment the previous problem is compounded
because I have my Scala source code under src/main/resources instead of
src/main/scala or src/main/java so the IDE does not know how to compile
things. I am still considering ways to resolve this. I do it this way
because as resources, the Scala source files are easy for my application to
deploy. The editor still does the basic lexical stuff, but not nearly
enough in terms of syntax and semantics. Essentially my development cycle
is (1) edit the Scala source in Eclipse, (2) copy/paste the source files
from Eclipse into my bin/src folder, and (3) run the utilities from the
command line and watch the Scala compiler complain about all my mistakes.
However, this is similar to the experience someone in the field would find
having to hack the utilities code at a customer site with no IDE or other
development tools."*
You'll also find seriously reduced functionality editing Java in Eclipse
when it's not considered part of your project's source tree and doesn't get
properly linked into the code DOM. So taking the original quote out of
context and implying it's a typical experience of Scala development is
somewhat disingenuous.
I suggest readers check out the full thing for themselves here though,
instead of relying on extracts:
https://groups.google.com/forum/?hl=en#!topic/scala-debate/gDFS9sKiD8I
> --
> Cédric
>
> --
> You received this message because you are subscribed to the Google Groups
> "The Java Posse" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/javaposse?hl=en.
>
--
Kevin Wright
mail: [email protected]
gtalk / msn : [email protected]
quora: http://www.quora.com/Kevin-Wright
google+: http://gplus.to/thecoda
<[email protected]>
twitter: @thecoda
vibe / skype: kev.lee.wright
steam: kev_lee_wright
"My point today is that, if we wish to count lines of code, we should not
regard them as "lines produced" but as "lines spent": the current
conventional wisdom is so foolish as to book that count on the wrong side
of the ledger" ~ Dijkstra
--
You received this message because you are subscribed to the Google Groups "The
Java Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
