Java at 30: The Genius Behind the Code That Changed Tech

Re:Java at 30: The Genius Behind the Code That Changed Tech by jbellis on Friday May 16, 2025 @11:22AM (#44006570)

more like 100x faster than Python/Ruby

and that's before you throw in real multithreading

[ Parent | on HN ]

Re:Java at 30: The Genius Behind the Code That Changed Tech by timbit42 on Saturday May 17, 2025 @12:31PM (#44015405)

I have heard around 50x, which is about the same as between assembly and BASIC on 8-bit systems.

[ Parent | on HN ]

Re:Java at 30: The Genius Behind the Code That Changed Tech by igouy on Sunday May 18, 2025 @12:20PM (#44022444)

We could measure programs.

[ Parent | on HN ]

Re:Java at 30: The Genius Behind the Code That Changed Tech by igouy on Sunday May 18, 2025 @12:10PM (#44022366)

Let's not pluck numbers out of thin air.

[ Parent | on HN ]

Re:Java at 30: The Genius Behind the Code That Changed Tech by jbellis on Monday May 19, 2025 @09:09AM (#44029459)

iirc these benchmarks have such short runtimes that they are not useful for assessing real-world java jit performance

[ Parent | on HN ]

Re:Java at 30: The Genius Behind the Code That Changed Tech by igouy on Monday May 19, 2025 @11:20AM (#44030803)

Is that a True Scotsman exclusion?

> iirc

    49.88—55.68 secs wall clock
    7.66
    5.51
    27.85—27.91
    83.79—87.16 
    10.94—11.09

How long a runtime would be required exactly, on what class-of hardware, to pass the True Scotsman?

Please provide alternative benchmarks that you accept.

[ Parent | on HN ]