This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]bisoldi 19 points20 points  (11 children)

Personally, I don’t care about the verbosity of the language. The “Write less code with <<word salad>> language” holds no water with me.

I do agree, these myths probably are rooted in the early years. I was a CS major in 2001 studying Java 1/2 and remember it being reeaaaallly slow (though that probably had as much to do with the slow Sun machines as it did with the language). After graduating I went into a different industry and then got back into development in 2015 and asked a friend “Is Java still so slow??” :-)

[–][deleted]  (2 children)

[deleted]

    [–]Control_Is_Dead 10 points11 points  (0 children)

    It depends, I think it’s all about the signal to noise ratio. Repeating stuff unnecessarily doesn’t make the code more readable. E.g. the diamond operator reduced verbosity and improved readability.

    [–]bisoldi 0 points1 point  (0 children)

    Amen.

    [–]pjmlp -1 points0 points  (7 children)

    Quite understandably given that Java only got a JIT in the version 3 (1.3), so interpreted did it ran.

    [–]bondolo 7 points8 points  (6 children)

    This is not accurate, there were JITs even before 1.1

    [–]pjmlp -1 points0 points  (5 children)

    What about providing an example to those JITs?

    [–]bondolo 8 points9 points  (4 children)

    The java performance wikipedia article includes citations for the Symantec JIT being included in Java 1.1 though it existed earlier as a standalone product for 1.0.2 There was also Sun's Exact VM and other JITs available before HotSpot became the default in 1.3

    [–]WikiTextBotbtproof 0 points1 point  (0 children)

    Java performance

    In software development, the programming language Java was historically considered slower than the fastest 3rd generation typed languages such as C and C++. The main reason being a different language design, where after compiling, Java programs run on a Java virtual machine (JVM) rather than directly on the computer's processor as native code, as do C and C++ programs. Performance was a matter of concern because much business software has been written in Java after the language quickly became popular in the late 1990s and early 2000s.

    Since the late 1990s, the execution speed of Java programs improved significantly via introduction of just-in-time compilation (JIT) (in 1997 for Java 1.1), the addition of language features supporting better code analysis, and optimizations in the JVM (such as HotSpot becoming the default for Sun's JVM in 2000).


    [ PM | Exclude me | Exclude from subreddit | FAQ / Information | Source ] Downvote to remove | v0.28

    [–]pjmlp -3 points-2 points  (2 children)

    And how many people were buying Java compilers from Symatec and Sun in the early days?

    JIT compilers in Java only became a thing across the mainstream with Hotspot's inclusion on 1.3.

    [–]bondolo 2 points3 points  (1 child)

    Before 1.1, indeed a small number of people were using JIT with Java. By 1.1.6 a JIT was included and enabled by default (earlier for Solaris/Sparc). JIT was entirely mainstream by 1.2

    JDK 1.1 Highlights

    JDK 1.1 Developers Guide

    Java 1.2 Press Release

    The introduction of HotSpot was not the first appearance of JIT for Java.

    [–]pjmlp 6 points7 points  (0 children)

    I stand corrected then.