I’m curious if there are things in the standard class library that you find useful but not widely used.

  • kaba0@programming.dev
    link
    fedilink
    English
    arrow-up
    8
    ·
    1 year ago

    HttpClient. You don’t necessarily need a third-party tool for rest calls or the like, and it really is quite handy!

    • Sheldan@programming.dev
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Finally a more sane API for HTTP requests in java. Still using a library tho, can be very convenient (like okhttp)

  • pohart@lemmyrs.org
    link
    fedilink
    English
    arrow-up
    7
    ·
    1 year ago

    Optional! I was reluctant at first because of the nullibility, but it’s so useful.

    I’m not sure this is what you were going for. I think most people know about optional and are skeptical because it’s not a fix for nullability.

    • BitPirate@feddit.de
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      Don’t forget its subtypes. OptionalInt, OptionalDouble etc. This avoids auto(un)boxing.

    • JackbyDev@programming.devOPM
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      I didn’t have a specific goal, but yeah I do wish more people used Optional.

      My one “gripe” with Optional (and I use it lightly) is that they mean for it to only be used as a return type instead of anywhere something can be optional. It can still be used as that though, they just don’t recommend it.

      • pohart@lemmyrs.org
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        IMHO it should be used for parameters, as long as there is more than one optional parameter. If rather all non nullable parameters though, which is usually doable.

        • JackbyDev@programming.devOPM
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 year ago

          I’ve waffled on it. Currently my opinion is to use whatever nullable annotation the project uses (if any, otherwise JetBrains’s). Essentially, I’m not sure if the official recommendation to avoid Optional for uses other than return types has reasoning I’m missing.

          I do use it like this though and lament that we don’t have an Elvis operator (?:)

          Optional.ofNullable(thingThatMightBeNull).map(e -> e.someMethod()).orElse(null);
          
            • austin@programming.dev
              link
              fedilink
              English
              arrow-up
              1
              ·
              edit-2
              1 year ago

              Optional has more syntactic sugar for more complex scenarios / functional call chaining that prevents repetitive if checks

              Optional.ofNullable(myObj)
                .map(MyClass::getProperty)
                .map(MyOtherClass::getAnotherProperty)
                .filter(obj -> somePredicate(obj))
                .orElse(null)
              

              This is completely null safe, the function calls are only made if the object is not null

    • JackbyDev@programming.devOPM
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      Link for the curious

      A PushbackInputStream adds functionality to another input stream, namely the ability to “push back” or “unread” bytes, by storing pushed-back bytes in an internal buffer. This is useful in situations where it is convenient for a fragment of code to read an indefinite number of data bytes that are delimited by a particular byte value; after reading the terminating byte, the code fragment can “unread” it, so that the next read operation on the input stream will reread the byte that was pushed back. For example, bytes representing the characters constituting an identifier might be terminated by a byte representing an operator character; a method whose job is to read just an identifier can read until it sees the operator and then push the operator back to be re-read.

      This does sound useful. I have to admit I don’t know much about InputStream and OutputStream and every time I need to do something with them (which is rare) I just search it up.

  • koreth@lemm.ee
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    Sometimes people who build low-level code with mutable state that’s shared across threads don’t know about some of the synchronization tools Java has. A lot of people know about synchronized, a lot of people know about semaphores, but fewer people seem to know about CountDownLatch and fewer still seem to have heard about Phaser. Those last two have saved me from having to implement my own synchronization code on a number of occasions.

    • JackbyDev@programming.devOPM
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      Those sound useful. I haven’t had to do much cross-thread synchronization thankfully, but I have had to use a BlockingDeque to check that some events came and in the right order. The CountDownLatch and Phaser may have been better.

    • austin@programming.dev
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      I had never heard of Phaser, but it looks pretty cool. I just read Baeldung’s Guide to Phaser and correct me if I’m wrong, but doesn’t it kind of seem like a race condition (it could just be how they use it in the examples)?

      class LongRunningAction implements Runnable {
          private String threadName;
          private Phaser ph;
      
          LongRunningAction(String threadName, Phaser ph) {
              this.threadName = threadName;
              this.ph = ph;
              ph.register();
          }
      
          @Override
          public void run() {
              ph.arriveAndAwaitAdvance();
              try {
                  Thread.sleep(20);
              } catch (InterruptedException e) {
                  e.printStackTrace();
              }
              ph.arriveAndDeregister();
          }
      }
      

      then

      executorService.submit(new LongRunningAction("thread-1", ph));
      executorService.submit(new LongRunningAction("thread-2", ph));
      executorService.submit(new LongRunningAction("thread-3", ph));
      

      if ph.arriveAndAwaitAdvance(); is called before all of the LongRunningActions are initialized, won’t it proceed before it is supposed to?

      • pohart@lemmyrs.org
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        Your analysis looks right to me. If this were mine I’d initialize all three before submitting any.

  • fabian@programming.dev
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    Not sure if it counts as not widely used, but I think the Collections.unmodifiable(Collection|Set|List…) methods are very useful.