Java 21 makes me like Java again

Post by _gabe_ » Sun, Sep 17, 2023, 9:30 PM UTC

MagicMoonlight wrote: post #667

_gabe_ wrote: post #665

Earlier quoted context omitted.

100% agree. You can create a HammerFactoryFactory to churn out HammerFactories in any language. But the ecosystem in Java (and C# is similar imo) promotes and encourages this type of problem solving. The one thing Java really does need is free standing (or namespaced) functions though. Sometimes I don’t want a class, what’s wrong with a function in a module or namespace in that case?

A class is a module/namespace. You can make a class just to have functions in it.

Post by bb88 » Sun, Sep 17, 2023, 9:48 PM UTC

za3faran wrote: post #452

jhaenchen wrote: post #164

Earlier quoted context omitted.

Agreed. Java injection frameworks are opaque and accomplish what they need to with overly powerful mechanisms because of the nature of the language. You don't see that sort of nonsense in python.

Nothing to do with the nature of the language, but with the nature of the program. If you're writing a few line script, you don't need a DI container. Once your program gets large, it becomes extremely messy without one. It's no surprise projects like [1] exist. [1] https://github.com/ets-labs/python-dependency-injector

    class MyClass:

        def __init__(self, my_dep1=None):
             if my_dep1 is None:
                 self.my_dep1 = get_my_dep1()  # Or potentially raise
             else:
                 self.my_dep1 = my_dep1

             [...]

    def test_my_class(): 
        mocked_dep1 = MagicMock()
        my_class = MyClass(my_dep1=mocked_dep1)
        [...]

Post by kaba0 » Sun, Sep 17, 2023, 10:04 PM UTC

Phelinofist wrote: post #658

MrBuddyCasino wrote: post #588

Earlier quoted context omitted.

Gradle is steaming pile of garbage. But since the zoomers are allergic to XML, Maven (actually fast) is slowly dying.

We are in the process of switching to Gradle at work and I'm not sure I like it. I used Gradle when building some OSS projects, but my experience wasn't that great.

Post by insanitybit » Sun, Sep 17, 2023, 11:27 PM UTC

palata wrote: post #349

insanitybit wrote: post #35

Earlier quoted context omitted.

No, there's a lot wrong with inheritance. It leads to all sorts of issues and while theoretically one can keep the tree 1 level deep, in practice it's too tempting to expand the hierarchy. This is one of Java's big issues. The other is reference equality as a default, pretty horrible. Records help but records are also limited in when they can be used.

> No, there's a lot wrong with inheritance. No, there is a lot wrong with bad code . No need to blame the language or any programming concept. Note that I say that for all programming languages, not just Java.

Post by erik_seaberg » Sun, Sep 17, 2023, 11:49 PM UTC

kaba0 wrote: post #485

adrianmsmith wrote: post #430

The "Sealed classes" feature, as described here, just feels all wrong to me. They are saying that if you have a (normal) interface, anyone can create a new class implementing it. So if you do if (x instanceof Foo) { ... } else if (x instanceof Bar) { ... } ... then your code will break at runtime if someone adds a new class, as that code won't expect it. So the article is saying the solution is to use the new "sealed…

It doesn't always make sense to allow extending -- String is `final` for a reason (and one might even argue that final should be the default, and one should explicitly mark with `open` classes that can be subclassed). The stereotypical FP example for sum types are a List -- there you only have an Element (T head, List tail) and a Nil(). There is no point extending it, it would, in fact, result in incorrect code in co…