Hacker News Reader

Comment by brabel | Hacker News Reader

When someone accuses Java of being an IDE-only language, I guess I'll use this argument as well because Java also always had javadocs which would allow you to see all type hierarchies, inherited methods etc which make Java, similar to Rust, hard to read without an IDE.

View on HN

I must have missed something but stdlib's javadoc is so horrendous. Yes it has exhaustive list of methods but it's devoid of actual programming content. No clear definition most of the time, no examples, no diagrams, no properties .. I swear on every remaining hair, everytime I have to visit these pages I go depressed. It was so much so that I wrote a json doclet to try to embed it into a repl to be able to experiment with actual objects with a bit of completion rather than having to waste precious time.

What’s the easiest way to access the javadocs for the transitive dependency closure of your project? I didn’t know about cargo docs until now, but it seems way more useful than javadocs. An good IDE still seems better than both, however.

I believe Maven supports this, but I don't know if it's turnkey like cargo docs.

Something like mvn javadoc:javadoc -DincludeDependencySources=true perhaps?

Last time I looked at a javadoc there was no search field at all, to say nothing of a FAYT across your entire set of dependencies.

It has had search field for a decade or so.

When Java appeared in 1995, my coding environment for it was XEmacs and Make.

Visual Age, JBuilder and Visual Café still took a while to come into being.

Reply on news.ycombinator.com