# Non-null is the Default

DevFeed: [Non-null is the Default](<https://devfeed.tech/articles/non-null-is-the-default-15782.md>)

Original publisher: [Read original article](<https://developer.squareup.com/blog/non-null-is-the-default>)

Author: Jesse Wilson

Published: 2017-05-13T17:27:56Z

Content type: article

Language: en

Sources: [Square Corner Blog RSS Feed](<https://devfeed.tech/sources/square-corner-blog-rss-feed.md>)

Topics: [Java](<https://devfeed.tech/topics/java.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [Library](<https://devfeed.tech/topics/library.md>), [changelog](<https://devfeed.tech/topics/changelog.md>)

Tags: [code](<https://devfeed.tech/tags/code.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [java](<https://devfeed.tech/tags/java.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [library](<https://devfeed.tech/tags/library.md>), [open-source](<https://devfeed.tech/tags/open-source.md>)

## AI overview

The article explains how Java nullability annotations, including package-level defaults, can make potential NullPointerExceptions visible to development tools. It also contrasts Java's approach with Kotlin's non-null-by-default type system and announces OkHttp 3.8, which is stricter about incoming nulls in three methods.

## Source excerpt

Using annotations to make Java's type system better