3 ms·
> lack of beginner-friendliness could also be seen as a lack of effective static analysis Slightly confusing comment to me ... Java has on the one hand a relat
by zmmmmm 5y ago
> lack of beginner-friendliness could also be seen as a lack of effective static analysis
Slightly confusing comment to me ... Java has on the one hand a relatively simplistic static typing system but on the other hand some of the best static analysis support that you can find (I don't think it's a coincidence; the relatively simple type system and lack of ways to hack around it facilitates the strength of the analysis that can be done).
I'm talking about things like, add a parameter to a method in a library and eclipse automatically not only deterministically renames it everywhere that its called in the library but in every dependent project, all in milliseconds. And a dozen other similar types of operations.
- oftenwrong 5y agoIn hindsight, I understand your confusion. I agree with your comment. Without static analysis tools like error-prone, findbugs, nullaway, checker framework, sonar, PMD, IDE-provided analysers, et cetera, it is easy to write problematic Java. On the other hand, the Java ecosystem has an abundance of such tools available and almost everybody is using them. (Hence, "but I do have that")