Java Sucks (So C# Didn't Have To) - Adele Carpenter - NDC London 2026

Java Sucks (So C# Didn't Have To) - Adele Carpenter - NDC London 2026

🎙 Adele Carpenter 👥 227K 📅 February 5, 2026 ⏱ 57 min 👁 4K 📄 expert opinion 🧭 2026-08-13
Available in: English (current) Français

Keywords

JavaC#genericstype erasurelanguage design

Summary

Adele Carpenter, a software engineer at Trifork Amsterdam, delivers a humorous and insightful talk at NDC London 2026 comparing Java and C#. She begins by acknowledging the rivalry between the two language communities and aims to bridge the gap. The talk traces Java’s history from its origins at Sun Microsystems in the 1990s, highlighting its design goals: simplicity, robustness, portability, performance, and dynamism. She explains how Java’s early decisions, such as type erasure in generics, were made due to deadlines and backward compatibility, and how they still impact developers today. Carpenter compares Java’s features with C#’s, noting that C# adopted many of Java’s concepts but improved upon them, such as reified generics. She discusses the influence of Xerox PARC languages (Smalltalk, Mesa, Cedar) on both Java and C#. The talk covers controversial design decisions, including checked exceptions and the evolution of the language through the Java Community Process. Carpenter emphasizes that Java’s stability and backward compatibility are its strengths, and she encourages developers to appreciate both languages. The talk concludes with a light-hearted call for unity among developers against common frustrations.

181 words

Critical Evaluation

Value of the Information & Strength of the Argument

The talk provides valuable insights into the historical and technical reasons behind Java’s design choices, particularly type erasure, and compares them with C#’s approach. Carpenter’s argumentation is well-structured, using concrete examples and anecdotes to illustrate points. She acknowledges trade-offs and presents a balanced view, avoiding pure bias. The discussion of Xerox PARC’s influence adds depth. However, some arguments rely on personal experience and may not be universally applicable.

Scientific Rigor, Source Quality, Title Accuracy

Carpenter cites historical facts and quotes from key figures like James Gosling and Brian Goetz, but does not provide formal citations. The talk is based on her expertise and public knowledge. The title is catchy but slightly misleading as the talk is more of a comparison than a pure critique. The content aligns with the title in that it discusses Java’s flaws, but it also highlights its merits.

151 words

Title / Content Match

The title is provocative and slightly misleading; the talk is more of a balanced comparison and love letter to Java rather than a pure critique. It does discuss Java's flaws but also its strengths.

Quality & Reliability

7/10

The talk is an expert opinion by a software engineer with practical experience in Java and C#. It provides historical context and technical explanations, but relies on personal anecdotes and subjective comparisons rather than empirical data. The information is generally accurate and well-reasoned, but not peer-reviewed.

Key Moments

Cited Sources

  • NDC Conferences — Conference organizer and event information.
  • NDC London — Specific conference event page.

Concurring Sources

Dissenting Sources

  • Java Generics FAQ — Provides detailed explanations of Java generics and type erasure, potentially offering different perspectives on the trade-offs.

External References

Contribution & Novelties

The talk offers a fresh perspective on the Java vs C# debate by focusing on historical context and design trade-offs. It provides a nuanced explanation of type erasure, often misunderstood, and highlights the influence of Xerox PARC. The speaker’s personal anecdotes add authenticity.

Pour aller plus loin :

90 words

Radar Profile

The radar profile shows high scores in information quantity and technical level, indicating a content-rich talk with moderate technical depth. The quality and reliability scores are slightly lower, reflecting the subjective nature of the presentation.

Reliability 7/10