Hacker Blogs
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 · #14639

B

Bruno's Journal

Personal blog · olympum.comprogrammingsystems

Bruno's Journal is a personal blog at olympum.com about programming and systems. Since 2011, 5 different Hacker News readers have linked it 6 times. The last post was in 2024, but the archive is still widely read.

Visit the blog
6mentions?
5HN people?
2011–2012first – last linked?
Links on Hacker News per year · peak 4 in 2011

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

Why HN links it

Bruno Fernandez-Ruiz's journal on Node.js versus Java performance and non-blocking I/O, plus the V8 governance debate. HN commenters link it as a source for benchmark figures and the Node/V8 discussion.

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

CTO by week, composer by weekend, triathlete by obsession

What Hacker News says?

  1. bluestix · 2012-06-25
    https://github.com/jbrisbin/node-vs-java-shootout http://vertxproject.wordpress.com/2012/05/09/vert-x-vs-node-... http://www.olympum.com/java/quick-benchmark-java-nodejs/ http://stackoverflow.com/questions/6645796/node-js-performan...

    Comment linking /java/quick-benchmark-java-nodejs/

    on “Blazing fast node.js: performance tips from LinkedIn”
  2. fosk · 2011-09-10

    Submitted NodeJS: To V8 or not to V8 as a story · 36 points

    HN discussion
  3. chapel · 2011-02-06
    Original article from Bruno Fernandez-Ruiz (Yahoo): http://www.olympum.com/future/nodejs-to-v8-or-not-to-v8/ Response to OP from Bruno: http://www.olympum.com/future/answering-jason-on-v8-governan...

    Comment linking /future/answering-jason-on-v8-governance-and-impact-to-nodejs/

    on “Joyent responds to Yahoo's issues with V8 being used under Node.js”
  4. nphase · 2011-09-11

    Submitted Ahead with node and V8 as a story · 2 points

    HN discussion
  5. agnokapathetic · 2011-10-30
    Java AIO $ ab -n 30000 -c 300 http://127.0.0.1:8080/ Concurrency Level: 300 Time taken for tests: 4.908 seconds Complete requests: 30000 Requests per second: 6112.65 [#/sec] (mean) Node (January 2011) $ ab -n 30000 -c 300 http://127.0.0.1:8124/ Concurrency Level: 300 Time taken for tests: 8.140 seconds Complete requests: 30000 Requests per second: 3685.69 [#/sec] (mean) http://www.olympum.com/java/java-aio-vs-nodejs/

    Comment linking /java/java-aio-vs-nodejs/

    on “What it means to be non-blocking in node.js”

Search all of HN for olympum.com