Java Is Underhyped

Post by slver » Fri, Apr 16, 2021, 9:36 AM UTC

nonbirithm wrote: post #110

The amount of vitriol Java receives in the game development space is rather strong. However, whenever people dismiss Java as being a bad language, I can't help but think of Minecraft. Yes, it's one of the few mainstream titles where Java has been successfully applied, but I believe Minecraft's success was specifically because it was written in Java. With no JVM, there would have been no Minecraft mods at the level of…

Post by cies » Fri, Apr 16, 2021, 9:37 AM UTC

theamk wrote: post #7

There are a few reasons to avoid Java today. - The programs are very verbose for the functionality they provide. There are countless lines of getters, setters, and trivial constructors. While IDE helps to write them, it makes reading existing programs slow and frustrating. Lombok helps, but very few programs use it. - If you do want to use Java ecosystem, there is Scala. It also has strong type system, nice IDE suppo…

Post by dragonwriter » Fri, Apr 16, 2021, 9:41 AM UTC

pydry wrote: post #218

BiteCode_dev wrote: post #213

Earlier quoted context omitted.

Design design does lead community culture. Java also had the unfortunate destiny of becoming popular at the time where "OOP all the thing" was a mantra in tech circles. Also design pattern were all the rage. Those things have a huge inertia, and while Java is not a much more flexible language, the image stuck, to the point that new comers still implement singletons in the wild.

Java created that hype to market itself. OOP all the things probably wouldn't have been a thing without it, for instance. It was very much a marketed language and a language designed to be sold to top heavy corporations. This fueled a lot of the crappy design decisions, the hype and the culture.

Post by twic » Fri, Apr 16, 2021, 9:42 AM UTC

erik_seaberg wrote: post #100

fomine3 wrote: post #91

Earlier quoted context omitted.

Stream API allows you to write fluent codes until you met checked exceptions. I wish they had solved this.

Java generics just aren't powerful enough to express that a higher order function's exceptions depend on its args, so pretty much everyone has given up on specific checked exceptions.

    @FunctionalInterface
    public interface ThrowingConsumer {
        void accept(T value) throws E;
    }

    public static  void forEach(Collection elements, ThrowingConsumer consumer) throws E {
        for (T element : elements) {
            consumer.accept(element);
        }
    }

    public static  Optional forEach(Collection elements, ThrowingConsumer consumer) {
        for (T element : elements) {
            try {
                consumer.accept(element);
            } catch (E e) {                 //