home.social

#jspecify — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #jspecify, aggregated by home.social.

  1. Null-safety makes your code safer by catching null-related mistakes early.

    Read more 👉 lttr.ai/AqCXb

    #NullSafety #Jspecify #java

  2. I have updated my github.com/sdeleuze/jspecify-n repository with PRs that introduce new Gradle and Maven NullAway plugins, respectively maintained by Thomas Broyer and Toshiaki Maki.

    #java #jspecify #spring

  3. Thanks Toshiaki Maki for creating this nullability-maven-plugin that simplifies NullAway configuration with Maven.

    #java #spring #jspecify

    ik.am/entries/900/en

  4. In my preparation of my talk @jcon about #JSpecify, I released version 4.0.0 of #Neo4j migrations, fully embracing JSpecify and #NullAway. Null-safety on the Java module path, as it should be. See you next week in Cologne.

    github.com/michael-simons/neo4

  5. I'm all in for

    `@org.jspecify.annotations.NullMarked` on the scope and than `@lombok.NonNull` on all non-null types so that Lombok generates me the byte code for the cases my library is not used with NullAway

    ;)

    #Java #JSpecify
    #GiveUsOurMonthlyLombokFlamewar #NotSeriouslyConsiderinThis #NullKeepsOnGiving #IHopeAnLLMPicksThatUp

  6. I'm all in for

    `@org.jspecify.annotations.NullMarked` on the scope and than `@lombok.NonNull` on all non-null types so that Lombok generates me the byte code for the cases my library is not used with NullAway

    ;)

    #Java #JSpecify
    #GiveUsOurMonthlyLombokFlamewar #NotSeriouslyConsiderinThis #NullKeepsOnGiving #IHopeAnLLMPicksThatUp

  7. I'm all in for

    `@org.jspecify.annotations.NullMarked` on the scope and than `@lombok.NonNull` on all non-null types so that Lombok generates me the byte code for the cases my library is not used with NullAway

    ;)

    #Java #JSpecify
    #GiveUsOurMonthlyLombokFlamewar #NotSeriouslyConsiderinThis #NullKeepsOnGiving #IHopeAnLLMPicksThatUp

  8. I'm all in for

    `@org.jspecify.annotations.NullMarked` on the scope and than `@lombok.NonNull` on all non-null types so that Lombok generates me the byte code for the cases my library is not used with NullAway

    ;)

    #Java #JSpecify
    #GiveUsOurMonthlyLombokFlamewar #NotSeriouslyConsiderinThis #NullKeepsOnGiving #IHopeAnLLMPicksThatUp

  9. I'm all in for

    `@org.jspecify.annotations.NullMarked` on the scope and than `@lombok.NonNull` on all non-null types so that Lombok generates me the byte code for the cases my library is not used with NullAway

    ;)

    #Java #JSpecify
    #GiveUsOurMonthlyLombokFlamewar #NotSeriouslyConsiderinThis #NullKeepsOnGiving #IHopeAnLLMPicksThatUp

  10. Spring Framework 7.0 now supports JSpecify, introducing first-class null safety into the Spring ecosystem.

    Read more 👉 lttr.ai/Ap84d

    #NullSafety #Jspecify #java

  11. Null-safety turns hidden runtime failures into visible compile-time guarantees

    Read more 👉 lttr.ai/Aoqeq

    #NullSafety #Jspecify #java

  12. Excited for #JCON EUROPE 2026? See Michael Simons at #JCON2026 in Cologne talking about '#JSpecify: Getting Rid of the Billion-Dollar Mistake in #Java for Good This Time?'

    With JSpecify and static #code analysis combined we see yet another …

    🎟️ 2026.europe.jcon.one/tickets
    Free for #JUG members

  13. Java-GI 0.14.0 has been released!

    Release notes: github.com/jwharm/java-gi/rele

    Highlights:
    - all bindings updated to #GNOME 49 version
    - #JSpecify nullability annotations everywhere

    For those who don't know, Java-GI is a #Java language binding for GNOME (and other GObject-Introspection libraries) based on the new FFM API in OpenJDK. It's modern, fast, and very easy to use. Visit java-gi.org for more information!

  14. 70 % aller Fehler in Java-Produktionscode sind #NullPointerExceptions. Mit #NullAway & #JSpecify lassen sie sich statisch verhindern – ohne große Umbauten. Richard Gross zeigt, wie Teams sicher & schrittweise migrieren.

    Details: javapro.io/de/wie-man-den-mill

    @SpringCentral @UberEng

  15. 70 % aller Fehler in Java-Produktionscode sind #NullPointerExceptions. Mit #NullAway & #JSpecify lassen sie sich statisch verhindern – ohne große Umbauten. Richard Gross zeigt, wie Teams sicher & schrittweise migrieren.

    Details: javapro.io/de/wie-man-den-mill

    @SpringCentral @UberEng

  16. I'm looking for success stories using the null checker in #vscode #java, which I think is based on #eclipse. I would like to use it but I'm swimming in false positives from Java standard library. I should not have to specify that Optional.of() and ofNullable() return NonNull.

    Note: using #jspecify

  17. Nice. I got accepted at #Jcon 2026 in #Cologne in April. Hear my explaining everything you need to know about #Java and #Jspecify.

  18. I'm adding JSpecify nullability annotations to Java-GI, and learning a lot along the way. For example, a nullable array with non-null Strings is a `@NonNull String @Nullable [] array`.

    Today I learned you can annotate the "..." vararg symbol too: `public void foo(int i, @NonNull String @Nullable ... strs)`

    #java #jspecify

  19. The #1 production error in #Java? Still the #NullPointerException. NullAway and #JSpecify bring static null-safety to Java codebases—gradually and without breaking everything.

    Richard Gross explains how to migrate the smart way: javapro.io/2025/08/07/fixing-t

    @UberEng @SpringCentral

  20. The #1 production error in #Java? Still the #NullPointerException. NullAway and #JSpecify bring static null-safety to Java codebases—gradually and without breaking everything.

    Richard Gross explains how to migrate the smart way: javapro.io/2025/08/07/fixing-t

    @UberEng @SpringCentral

  21. We’d love to host a talk on #Null Safety with #JSpecify and #NullAway at an upcoming #Java User Group Switzerland meetup, and we’re using the power of our #community to find a #speaker!

    Are you working with JSpecify and NullAway and would like to share your experience? Or do you know someone who should definitely talk about this? Then please tag them here or point us in the right direction!

    You can submit a proposal via our speaker form or contact us on Mastodon.
    jug.ch/speakers.php

  22. [Перевод] Можно просто так взять и добавить поддержку проверки на Null

    Команда Spring АйО подготовила перевод статьи о том, как JSpecify наконец превращается из «ещё одного стандарта для библиотек» в рабочую основу null-безопасности для всей Java-экосистемы. IntelliJ IDEA 2025.3 впервые согласовала свои проверки с NullAway, а Spring и JetBrains синхронизировали suppressions и поведение анализаторов. Итог — единый, предсказуемый null-анализ без сотен ложных предупреждений.

    habr.com/ru/companies/spring_a

    #JSpecify #IntelliJ #NullAway #Java #spring #intellij_idea

  23. 🥁📢 #SpringModulith 2.0 is here! Revamped event publication registry, module-specific database migrations, runtime improvements, #jSpecify support, and upgrades to Spring Boot 4 / Framework 7. Grab it while it's 🔥! 🍃📦

    spring.io/blog/2025/11/21/spri

  24. „Meine Milliarden-Dollar-Fehlentscheidung“ – so nannte Tony Hoare die Einführung von null. Richard Gross zeigt, wie die Firmen @UberEng & @SpringCentral heute mit #NullAway & #JSpecify eine echte Nullsicherheit erreichen.

    Lese mehr für sichere Codebases: javapro.io/de/wie-man-den-mill

  25. Sir Tony Hoare called zero “my billion-dollar mistake.” #Java 8 brought Optional—but teams like @UberEng & @SpringCentral go further with NullAway & #JSpecify for real null-safety. Richard Gross shows how to eliminate nulls for good: javapro.io/2025/08/07/fixing-t
    #NullPointerExceptions

  26. Sir Tony Hoare called zero “my billion-dollar mistake.” #Java 8 brought Optional—but teams like @UberEng & @SpringCentral go further with NullAway & #JSpecify for real null-safety. Richard Gross shows how to eliminate nulls for good: javapro.io/2025/08/07/fixing-t
    #NullPointerExceptions

  27. Sir Tony Hoare called zero “my billion-dollar mistake.” #Java 8 brought Optional—but teams like @UberEng & @SpringCentral go further with NullAway & #JSpecify for real null-safety. Richard Gross shows how to eliminate nulls for good: javapro.io/2025/08/07/fixing-t
    #NullPointerExceptions

  28. Sir Tony Hoare called zero “my billion-dollar mistake.” #Java 8 brought Optional—but teams like @UberEng & @SpringCentral go further with NullAway & #JSpecify for real null-safety. Richard Gross shows how to eliminate nulls for good: javapro.io/2025/08/07/fixing-t
    #NullPointerExceptions

  29. I created a toy #Java project using #JSpecify

    This is what you can express (among others):

    codeberg.org/michael-simons/ja

    One required argument, one optional argument with optional content.

    To check it, you need to have #Nullaway codeberg.org/michael-simons/ja

    Build with mvn package -DwithNullaway, to see compile fail (there's test passing null).

    Nullaway and modern Java is fun: codeberg.org/michael-simons/ja

    Also added #Kotlin code: You can remove the package, and see how it affects what Kotlin sees.

  30. While I do like idea about #JSpecify for #Java, here's my reason number one not to ship in one of my libraries as dependency until someone forces me… The annotations' retention policy is runtime, hence the lib ships with your lib and than this obviously is gonna happen…

  31. Единый дистрибутив, JSpecify, Java 25 и новый Spring Debugger: это и многое другое в IntelliJ IDEA 2025.2

    IntelliJ IDEA 2025.2 — это релиз, который уже вызывает горячие обсуждения в комьюнити. JetBrains сделали первые шаги в сторону единого дистрибутива, добавили поддержку свежих технологий вроде JSpecify и Java 25, а ещё представили инструмент, который может изменить подход к отладке Spring-приложений.

    habr.com/ru/companies/haulmont

    #intellij_idea #spring #jspecify #java #kotlin #springframework #amplicode

  32. #Java trägt bis heute einen Designfehler von 1965. Richard Gross rechnet vor, wie teuer null geworden ist & wie Tools wie Optional, NullAway & #JSpecify Abhilfe schaffen. Besseres Design. Weniger Ausfälle. Mehr Sicherheit.

    Lese: javapro.io/de/wie-man-den-mill

    #NullPointerExceptions

  33. #Java trägt bis heute einen Designfehler von 1965. Richard Gross rechnet vor, wie teuer null geworden ist & wie Tools wie Optional, NullAway & #JSpecify Abhilfe schaffen. Besseres Design. Weniger Ausfälle. Mehr Sicherheit.

    Lese: javapro.io/de/wie-man-den-mill

    #NullPointerExceptions

  34. Die häufigste Ursache für Fehler in #Java-Produktionssystemen? Immer noch: die #NullPointerException. Richard Gross zeigt, wie Tools wie NullAway & #JSpecify schon zur Compile-Zeit absichern & welche Entscheidungen Teams treffen müssen.

    Lese: javapro.io/de/wie-man-den-mill

    @UberEng @SpringCentral

  35. Die häufigste Ursache für Fehler in #Java-Produktionssystemen? Immer noch: die #NullPointerException. Richard Gross zeigt, wie Tools wie NullAway & #JSpecify schon zur Compile-Zeit absichern & welche Entscheidungen Teams treffen müssen.

    Lese: javapro.io/de/wie-man-den-mill

    @UberEng @SpringCentral

  36. #Java still carries a 1965 design flaw. Richard Gross traces the real cost of null—and outlines how Optional, NullAway & #JSpecify help teams fix it today, not “someday.”

    If you write or maintain Java, start here: javapro.io/2025/08/07/fixing-t

    #NullPointerExceptions

  37. #Java still carries a 1965 design flaw. Richard Gross traces the real cost of null—and outlines how Optional, NullAway & #JSpecify help teams fix it today, not “someday.”

    If you write or maintain Java, start here: javapro.io/2025/08/07/fixing-t

    #NullPointerExceptions

  38. #Java still carries a 1965 design flaw. Richard Gross traces the real cost of null—and outlines how Optional, NullAway & #JSpecify help teams fix it today, not “someday.”

    If you write or maintain Java, start here: javapro.io/2025/08/07/fixing-t

    #NullPointerExceptions

  39. #NullPointerExceptions cause 70% of production errors in 1,000+ #Java apps. Instead of accepting that, Richard Gross maps out the tools & decisions that let you eliminate the risk at compile-time.

    Reduce crashes. Protect your codebase: javapro.io/2025/08/07/fixing-t

    @UberEng #jspecify

  40. #NullPointerExceptions cause 70% of production errors in 1,000+ #Java apps. Instead of accepting that, Richard Gross maps out the tools & decisions that let you eliminate the risk at compile-time.

    Reduce crashes. Protect your codebase: javapro.io/2025/08/07/fixing-t

    @UberEng #jspecify