Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #15627

J

Julien Ponge

Personal blog · julien.ponge.org/blogprogramming

Julien Ponge's personal blog at julien.ponge.org covers programming. Since 2014, 5 different Hacker News readers have linked it 5 times, most often “Analysing the Performance and Costs of Reactive Programming Libraries in Java”. It is still writing: the last post was on 2026-08-05, and you can follow it by feed.

Visit the blog
5mentions?
5HN people?
2014–2023first – last linked?
Links on Hacker News per year · peak 2 in 2021

Too few sampled comments (2) to say how often HN recommends it.?

Why HN links it

HN readers link Julien Ponge's posts on Java streams versus reactive code performance and maintainability, and on contributor license agreements. Commenters cite them as supporting points, not as recommended reads.

Summarised by Claude from a sample of 2 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

Julien Ponge

Most-linked posts?

  1. Analysing the Performance and Costs of Reactive Programming Libraries in Java
    2 people · 2 mentions · first linked 2021-10-21

What Hacker News says?

  1. Java streams don’t infest your project. They also don’t throw away the error system of the language. They are also leagues more maintainable than a reactive project. Ignoring the maintenance issues, reactive applications do not yield better performance on realistic I/O-bound workloads: https://julien.ponge.org/blog/publication-performance-and-co... So all you end up with is less maintainable code and more developer…

    Comment linking /blog/publication-performance-and-costs-of-reactive-programming-libraries-in-java/

    on “Angular 13”
  2. Submitted Analysing the Performance and Costs of Reactive Programming Libraries in Java as a story · 3 points

    HN discussion
  3. This is basically a BSD/MIT license plus a CLA/DCO style clause. Please don't create a new license; just use ones that already exist. https://julien.ponge.org/blog/in-defense-of-contributor-lice... http://elinux.org/Developer_Certificate_Of_Origin

    Comment linking /blog/in-defense-of-contributor-license-agreements/

    on “Show HN: The “No Fluff” License”
  4. Submitted The Mozilla Public License Version 2.0: A good middle ground? (2012) as a story · 1 points

    HN discussion
  5. Submitted Developer Certificate of Origin versus Contributor License Agreements as a story · 1 points

    HN discussion

Search all of HN for julien.ponge.org