Don’t call it a comeback: Java is still champ

Post by zinxq » Tue, Aug 09, 2022, 6:32 PM UTC

zinxq wrote: post #54

5e92cb50239222b wrote: post #35

Earlier quoted context omitted.

Java is heavily used in high-frequency trading. I believe it's the most popular language after C++.

Indeed. Shutoff Garbage collection completely and it can work. (And make sure your Java code creates no garbage - which is a new type of programming in and of itself)

Post by shagie » Tue, Aug 09, 2022, 6:35 PM UTC

mindslight wrote: post #60

NoSorryCannot wrote: post #10

Earlier quoted context omitted.

Whoever invented the car analogy should pay for what they did.

Indeed. All cars suffer the same speed limits and traffic, so how effective your car is ultimately depends on how you drive within those constraints. The analogy slyly condenses everything down to some car-manufacturer-marketing version of "fun", betraying both spirited drivers and whatever topic it is applied to. Since we're throwing out analogies, Java-the-language is more like a riding lawnmower. It is capable of…

Post by bitwize » Tue, Aug 09, 2022, 6:40 PM UTC

ska wrote: post #89

xxpor wrote: post #73

Earlier quoted context omitted.

An uncommon but not unheard method around that (in services that have diurnal patterns) is to throw memory at it and collect once a day during the down time. You can take the server out of service, restart it, and put it back in service.

I read this was semi-standard memory management in the early lisp machine days, because that gc was so slow.

Post by pkolaczk » Tue, Aug 09, 2022, 6:43 PM UTC

mcculley wrote: post #188

sushisource wrote: post #139

Earlier quoted context omitted.

> This combined with the fact that Java doesn't crash Huh? Doesn't crash in what way vs. C? I can still deref a null pointer and blow up. Java's perfectly fine, and I have no idea why you'd write C any more, but if you care about (extreme) performance and not crashing, Rust seems the obvious modern choice here.

I have worked on big projects with up to ~100 developers. On the C projects, someone's null-pointer dereference brings down the whole process. On the Java projects, the event handler or daemon thread has an exception handler at the top that logs the error and keeps executing. This is a huge difference in behavior. Sometimes, you want to fail fast and be forced to fix that bug. More often, I want to keep doing whateve…

Post by gavinray » Tue, Aug 09, 2022, 6:51 PM UTC

dkarl wrote: post #225

abadger9 wrote: post #22

I've used Java my entire career and i'm fortunate for it. I appreciate how readable the code is (unlike my experience with Erlang, Haskell, etc), typically i don't have foundational issues in the web framework (once again had some with Haskell). Everything works, if I need to do low latency, there's great libraries and resources, if i need to build a simple internal tool, it can be done effortlessly. I think python i…

Agree with all of that except readability. Java has some language deficiencies (no first-class functions, "streams" missing for almost twenty years and added too late to be done elegantly) and some cultural norms (mutable everything, overuse of inheritance) that make it a chore to read most of the Java code you encounter in the wild, including the source code of the libraries you depend on. Figuring out the behavior…

    static void main() {
        BiFunction add = (Integer x, Integer y) -> x + y + 5;
        Integer result = addTo(10, add);
        Integer result2 = addTo(10, (x, y) -> x + y + 5);
    }

    static Integer addTo(Integer acc, BiFunction addFn) {
        return addFn.apply(acc, 5);
    }

    Integer eval(Expression e) {
        return switch (e) {
            case INT(var value) -> value
            case ADD(var left, var right) -> eval(left) + eval(right)
            case MULT(var left, var right) -> eval(left) * eval(right)
        }
    }