3 ms·
It's interesting to see this right on the tail of https://jspecify.dev/blog/release-1.0.0/ https://jspecify.dev/blog/release-1.0.0/ by Meta et al. That was don
by rendaw 2y ago
It's interesting to see this right on the tail of https://jspecify.dev/blog/release-1.0.0/ https://jspecify.dev/blog/release-1.0.0/ by Meta et al. That was done AFAIK because JEP-305 died and it didn't seem like Oracle was going to ever do anything about it. Did Oracle do nothing to coordinate here?
- tadfisher 2y agoI think you mean JSR-305 [1]. Even though the initiative died in committee, you can still use the reference implementation [2] and hundreds of thousands of projects do so. Most static analysis tools and IDEs support it as well. JSpecify takes advantage of Java 8 features (e.g. annotations on generic type parameters), so it's strictly better, and I believe at least the IntelliJ IDEs support it. [1]: https://jcp.org/en/jsr/detail?id=305 https://jcp.org/en/jsr/detail?id=305 [2]: https://central.sonatype.com/artifact/com.google.code.findbugs/jsr305 https://central.sonatype.com/artifact/com.google.code.findbu...