Java Polls

There is another interesting library for null-safety in Java called JSpecify: jspecify.dev/docs/user-guide But its not listed above as option because it is not sufficiently used yet.

Things referred in the options: Optional: docs.oracle.com/en/java/javase… @jetbrains Annotations: jetbrains.com/idea/docs/Null… @CheckerFrmwrk Nullness checker: #htoc14" target="_blank" rel="nofollow noopener">checkerframework.org/releases/0.8.4…

How do you deal with nullability in Java? Comment if none or combination of these.

@cmogoncalves That is a good approach. And perhaps when the type is too long with nested type-parameters.

As a Java programmer, I use var (local variable type inference)… If your answer is “sometimes”, comment why/when.

This does not happen while evaluating expression 'p1 instanceof Point point' and therefore x() and y() methods don't get executed.

The correct answer is C. The expression 'p2 instanceof Point(int x, int y) point' not only matches p2 with Point to create a variable point, but also deconstructs it into variables x and y. To do that it uses accessor methods x() and y() and therefore they get executed.

What do you think will be the output of this, assuming you run it with Java 19 (preview enabled)? See poll below.

@s3ndn00d7 That sounds interesting.

@JavaPolls DogeCloud

Which cloud service do you use for your Java applications?

@AhmadBawaneh1 @dominokit Nice! Good luck with upcoming features and releases.

@JavaPolls @dominokit Yes we use #GWT as a compiler but also compatible with #j2cl we don't use #GWT widgets, all components are elements based, we are now in the process of making a new release with theming support and will be a start for implementing templating and bi directional databind.

For your Java backends, what do you use on the frontend? Java, JavaScript or something else.

@AhmadBawaneh1 @dominokit That looks good. It seems it uses GWT. Another great Java toolkit for building web UI.

@JavaPolls I use @dominokit

@GKlijs True. orElseThrow() is much better name than get(). It depicts the side effect clearly.

@JavaPolls Semantically it's different through. I like it as a quick way to handle them, where when needed a specific exception can be put in later.

Optional: what do you think about it?Choose from: 1. It has helped improve null-safety/ readability 2. It could have been designed better 3. Both For any of the choices, if you want to provide arguments, the comments section is open.

@GKlijs That’s true. The no-argument one was not present in Java 8. In fact, it does exactly the same thing as get(). Perhaps they want to deprecate get() which would be a good thing for Optional.

@JavaPolls Not the one without a supplier as argument, #orElseThrow" target="_blank" rel="nofollow noopener">docs.oracle.com/en/java/javase…() 😉.

@WhiteWoodCity Can you elaborate what should be solved by primitive? And how?

@JavaPolls I think it should be solved by primitive class

@GKlijs orElseThrow() was there in Java 8. But some good additions were done later on like or(), ifPresentOrElse(), stream(), filter(), map() etc. One problem is get() looks so innocent, but it throws an exception for the “empty” scenario.

@JavaPolls It's a shame things like orElseThrow were not in Java 8, but we're getting there.

Preview features are provided with a JDK release for developers to experiment with them and provide feedback. Have you ever used preview features for any JDK release?