findbugs

Actually there have been PRs. At the moment there are 15 PRs sitting on FindBugs' Github page: https://github.com/findbugsproject/findbugs/pulls 5 of them are over a year old. Most of them had no review by the development team, and many of those that did, got stuck on Bill, for instance, trying to get Travis enabled: https://github.com/findbugsproject/findbugs/pull/48#issuecom... There is no incentive to contribute to a project in such poor shape. SonarQube abandoned FindBugs mainly because it was low on activity: "FindBugs project activity: The activity on the project is quite low and thus the value coming out of it does not come fast enough to satisfy our users." http://www.sonarqube.org/sonarqube-java-analyzer-the-only-ru...

>Except these aren't at all the same. With a reference, you have no good way of telling whether your reference IS nullable. As the article mentions, we have annotations to do just that. >Therefore it is trivial to a) train developer habits to always check before fetch, and b) enforce an isPresent check with static checks. Again, if we're using static analysis to verify the correct use of Optional, why are we using optional at all? Why wouldn't we use static checks to verify null references can't be dereferenced, instead of hypothetical yet-to-be-implemented static checks that may not be implemented anyway? See https://github.com/findbugsproject/findbugs/issues/56

That is the old bug tracker. An issue was submitted on the official tracker and immediately closed. See https://github.com/findbugsproject/findbugs/issues/56 for explanation.