Java With Us

About Java With Us

Who we are, how we write, and what you can expect from this site.

Java With Us is a long-running reference site for Java developers, online since 2013. The site covers the Java language, the JVM ecosystem, build tooling, common errors and the free developer tools that make day-to-day Java work faster. Primary language is English; a subset of content is available in French and Italian.

What this site is for

Every article on Java With Us answers a concrete question a developer would type while staring at their editor:

  • "How do I install Java 21 on Ubuntu?"
  • "What does static actually mean?"
  • "Why is my NullPointerException happening here?"
  • "Java vs Kotlin — which should my team adopt for a new Android project?"

We keep answers short, show runnable code, and link out to the authoritative source (Oracle docs, JEPs, the Java Language Specification, RFCs) wherever one exists.

Who writes the content

Content is produced by a small editorial team of working Java developers with combined experience across back-end services (Spring Boot, Jakarta EE), Android, JVM internals, and DevOps tooling. We are deliberately not a content farm — every page is hand-written and reviewed against real-world use. The editorial lead is Daniel Whitaker, a Bay Area software engineer who has been writing Java since the original 1.0 release in 1996 — 30 years in the language across finance back-ends, early Android, the Spring and Hibernate era, and the modern Spring Boot / JVM stack. Daniel runs Java With Us as a long-term educational project alongside his day job.

To reach the editorial team: contact page.

Editorial commitments

Four rules apply to everything published:

  1. Working code over hand-waving. Every snippet can be copy-pasted into a .java file and compiled. When a snippet requires a library (Jackson, Lombok, JJWT), we flag it explicitly.
  2. Modern Java first. Examples target Java 17 (LTS) and Java 21 (LTS) unless the topic is specifically about a legacy version. Where the legacy idiom is still common in the wild (SimpleDateFormat, raw HashMap iteration, anonymous inner classes where a lambda works), we show it alongside the modern version so you can recognise both in real codebases.
  3. No filler. No SEO-padded intros, no "what you will learn" bullet lists, no "conclusion" that repeats the intro. If a topic genuinely needs 3 paragraphs, it gets 3; if it needs 12, it gets 12.
  4. Corrections are public. When a reader flags an error, we fix the article and keep a brief note where the change matters. See the editorial policy for details.

Who this site is for

  • Students learning Java for coursework or a first job — the Learn, FAQ and Glossary sections are written with you in mind.
  • Professional developers hitting a specific error or needing a quick refresher — use the search box or jump straight to the relevant tool or FAQ entry.
  • Developers migrating from Python, JavaScript, C++ or Kotlin — see the comparison pages.

How we fund the site

Java With Us is supported by display advertising (Google AdSense) and by direct reader donations when available. Ads are clearly marked, never inserted inside code blocks or between paragraphs in a way that interrupts reading, and never disguised as content. Nothing on this site is paid placement — when we recommend a specific JDK, tool, or library, it is because we actually use it or have specific reasons to prefer it. See the funding and disclosure section of the editorial policy for the long version.

Our sources

Technical facts are cross-checked against:

  • Oracle documentation — the official JDK API docs and installation guides at docs.oracle.com/en/java/javase.
  • Java Enhancement Proposals (JEPs) — the formal design docs for every Java feature, at openjdk.org/jeps.
  • The Java Language Specification (JLS) — the authoritative reference for language semantics.
  • JDK vendor docs — Adoptium Temurin, Amazon Corretto, Microsoft OpenJDK, Azul Zulu for installation and packaging specifics.
  • The OpenJDK mailing lists and bug tracker when a detail is not settled in the official docs.

Contact

To report an error, suggest a topic, request a correction, or exercise your GDPR rights: contact page. Reader feedback is one of the main drivers of what gets written next.