3 ms·
Obviously. If the docs are garbage then you are going to have to find alternatives. However these days devs have never had it better.
by net_greybeard 5y ago
Obviously. If the docs are garbage then you are going to have to find alternatives. However these days devs have never had it better.
- Ygg2 5y agoLaughs in shitty Oracle docs.
- net_greybeard 5y agoI've worked in a lot of places where there were no docs and nobody knew how any worked. So be thankful that you have some docs.
- Ygg2 5y agoAnd I've worked with auto generated meta code in Java 1.3. In practice, difference between it and Oracle docs was negligible. Hell. Their auto-gen code was more self explanatory than Oracle Java Docs.
- lostcolony 5y agoI personally enjoy the Javadocs that tell me nothing about how to use the damn thing. Spending hours poring over it, with no examples, just a generated Javaoc version of the static types my IDE would have told me, and through much trial and error, I eventually figure out that I need - new Doer(UnrelatedFactory.create("foo", new WTFBar(), 5, null, null), RandomEnumFromADifferentPackage.MEANINGLESS_VALUE, true).do() But I'm not really convinced such documents are helpful. I mean, technically they're better than nothing (as in, literally better than nothing), but the difference between nothing and those docs is so small it approaches nothing ('as the worthlessness of the documentation approaches infinity the value of reading them approaches nothing', as it were)