Expand Authors Top

If you have a few years of experience in the Java ecosystem and you’d like to share that with the community, have a look at our Contribution Guidelines.

Expanded Audience – Frontegg – Security (partner)
announcement - icon User management is very complex, when implemented properly. No surprise here.

Not having to roll all of that out manually, but instead integrating a mature, fully-fledged solution - yeah, that makes a lot of sense.
That's basically what Frontegg is - User Management for your application. It's focused on making your app scalable, secure and enjoyable for your users.
From signup to authentication, it supports simple scenarios all the way to complex and custom application logic.

Have a look:

>> Elegant User Management, Tailor-made for B2B SaaS

Java Top

Get started with Spring 5 and Spring Boot 2, through the Learn Spring course:

> CHECK OUT THE COURSE

 1. Overview

In this article, we'll comment on the similarities and differences between the methods Paths.get() and Path.of().

2. Identical Behavior

The Path.of() method takes a URI as an argument and converts it into the Path of the associated object.

Let's now have a look at the code of Paths.get():

public final class Paths {
    public static Path get(URI uri) {
        return Path.of(uri);
    }
}

As we can see, the only thing Paths.get() does is call Path.of(). Therefore, the two methods return an identical result.

3. The Differences Between the Methods

We'll now comment on the difference between those two methods.

3.1. Introduction Version

Before Java 8, it was not possible to define a default static method inside an interface. Hence Path needed a companion interface, Paths. All the factory methods were defined in Paths at this time.

Then this limitation was removed, and in Java 11, the code of the factory method has eventually been moved to the Path interface. Additionally, the code of Paths.get() was updated to defer to Path.of(). Paths.get() was indeed kept to ensure backward compatibility.

3.2. Naming Pattern

The code was not only moved, but the name of the factory method did also change. The problem with the original name is that it looks like a getter. However, Paths.get() doesn't get anything that belongs to the Paths object. The standard name for static factory methods in Java is of. For instance, EnumSet.of() follows this pattern. As a consequence, the new method was called Path.of() for consistency purposes.

4. Which One Should We Use?

If we're working with a version between Java 7 and 10, we have no other choice but to use Paths.get(). Otherwise, if we're working with a later version, we should go for Path.of(). The Paths class may indeed be deprecated in a future Java release, as it's stated in the class' comments. Moreover, using directly the factory method from Path spares an additional input.

5. Conclusion

In this tutorial, we've understood that the two identical methods, Paths.get() and Path.of(), coexist for some historical reasons. We've analyzed their differences and concluded with the most suitable fit for us depending on our situation.

Java bottom

Get started with Spring 5 and Spring Boot 2, through the Learn Spring course:

>> CHECK OUT THE COURSE
Generic footer banner
Comments are closed on this article!