Hey Coders!!
A lot of you have been telling me that rust is soon going to replace java.
Looking at the perspective of the number of people using java, I would say Rust isn't going to replace java.
I don't think a language can fully replace another one.
Oracle released Java in 1995. It is still used worldwide by so many developers out there.
I mean, sure, Java is pretty lengthy and we need another way to make it easier to write code.
Technologies such as Rust and Go function the same way as Java but they are written in shorter code.
Hello World Written in Java:
class Simple{
public static void main(String args[]){
System.out.println("Hello Java");
}
}
Hello World Written in Rust:
fn main() {
println!("Hello world!");
}
Well, Rust does have a lot of new more interesting ideas and concepts but we don't know whether they are going to be adopted universally.
There are also a lot of other companies that have java code written in their programs.
One advantage of using Java is that you have a lot of libraries and APIs available.
Well, Rust doesn't really have as many developers as Java does.
Rust might not be large enough to become a conventional language.
The Final Reason why I think Java won't be replaced is because the entire company of Android has a lot of servers that run on Java.
Overall, There is a possibility that Rust could replace Java but it most likely wont.
I hope I answered your question and I hope you enjoyed this blog!
And don't forget...
Top comments (73)
I don't know much about Rust, but from what I gather, it has about the same chance of replacing Java as JavaScript replacing C in the Linux kernel. Would make roughly the same amount of sense too.
Also, 3 vs. 5 lines in a hello world program proves what exactly?
I doubt rust would replace Java but it defo has more of a Chance replacing Java than JS has replacing C.
Rust is intended to actually replace C++; it adds all the safety features needed to make responsible code with C/C++, but brings a modern syntax with what I'd say is by far the most helpful compiler ever.
If I want to build a desktop GUI app using GTK, I would certainly pick C++, because Rust executable size is big and takes very long to compile.
Err... and the C++ one will likely have bugs and race conditions, and the Rust one won't.
Do you not understand the value proposition of Rust?
Rust has less boilerplate here, but only because there is nothing that needs error checking or making the borrow checker happy. I suspect a thirty line piece of java ported to scala and rust would have the fewest lines in scala. Java probably comes in slightly smaller than rust, but could easily be a little bigger.
I guess this isn't about the number, but the length of the lines. You can have less lines, but with a bigger length.
Oracle did neither create nor release Java. It was Sun Microsystems, which Oracle acquired in 2010.
Looks like author have no idea
I don't know about rust but I think kotlin is better in terms of development experience and most of the time kotlin code is concise and shorter than java code.
Yes, but Kotlin was designed with this exact mentality. Java plus some features, minus some annoyances, basically.
While I assume that you can do most things in Rust, it is primarily a speed and memory safety focused language. Without garbage collection, I might add. That does not make Rust bad, obviously, but I genuinely don't see the point of this article.
And adding some other annoyances, like not being able to use Java 17 together with Kotlin at the moment.
Right.
I was actually wondering about that. Is Kotlin supposed to be compatible with Java in the future as well? If not, major RIP.
True.
Yes, and likely it's won't be much longer before Java 17 is supported. Spring is likely to take a year before going to 17. If it's not possible by then, it's going to be a major deal breaker. Originally people used Kotlin mostly because they were stuck on also JVM's with Android. Kotlin also has other compile targets, like native and js. But I think they are still used very little.
Despite all the differences between the two languages, Java and Kotlin are 100% interoperable. You can call Kotlin code from Java, and you can call Java code from Kotlin.
Not 100%, you can't call a coroutine from Java, and you can't use Java Code that contains records for the moment. But yes, it all runs on the JVM, as does Scala, Groovy and Clojure, which you could use all together in one app.
Seems you can use Java records with Kotlin (and even define them in Kotlin)
kotlinlang.org/docs/jvm-records.ht...
Conciseness per se is pointless. Development productivity is only thing that matter when comparing Kotlin and Java. And Kotlin often is worse than Java in this regard. At least for backend development.
Do you have personal experience with this? I wonder if this will change with time as people adapt to using the language more. In my area, Kotlin jobs or even projects are still very rare unfortunately, so please elaborate.
This might change over the time, but odds are low since some issues are inherent to Kotlin as a language. Here is my answer on similar question with more details and my personal experience.
I should note, that many Java issues, which make people consider Kotlin, can be solved by adopting Pragmatic Functional Java in combination with Java 11 and up (especially Java 17).
While I like Rust a lot and consider its approach to resource management brilliant, I believe that Rust has very little chances to replace Java. First and foremost, it has no sensible advantages for enterprise app development - main Java use case. Rust is still more complex to use than Java and Java still has much more developers than Rust.
βTechnologies such as Rust and Go function the same way as Java but they are written in shorter code."
This is not true, it's much fairer to say it's all 3 different beasts, with their own strengths, once you want more than hello world.
I'm not very familiar with Go, so this might not be totally fair. But Go seems the best language for programs around networking, which don't need a lot of additional dependencies.
Java is mostly great for it's vast ecosystem, and Spring Boot. With it's easily to hook on almost any database, and expose is as you want, even 'official' with GraphQL lately. Also don't forget all the tools around it's JVM runtime for performance / safety etc.
Rust is nice when performamce is important, and when you want to reduce some categories of errors. The price to pay is that you need more time to program. Compared to Java and Go the core language is tiny. Even for random getting numbers you need a library. The ecosystem does get better. But when you want to connect to databases, or when dealing with formats like Avro its not as smooth as Java. And using Protobuf is possible, but not as smooth as with Go.
Some others mentioned already, probably no language will totally replace another language. I can imagine some things on the backend, I did in the past with Java, can be done with Rust now. But to be fair at the moment it would not be my first choice.
It's still good to know multiple languages, and there relative strengths through.
On May 27, 2008 Ted Neward published Dead like COBOL - Is Java ripe for replacement?.
And here we are 13+ years later. That type of legacy has enormous inertia.
If anything (one of my pet hypotheses is that) Google developed Go to de-emphasize the importance of Java within that organization:
Java also can produce standalone binaries, but this is not so often necessary. Didn't get your phrase about harassment. Perhaps it's something only you can feel.
P.S. I wrote commercial Go code and worked at Google (and their monorepo), so I know what I'm talking about.
You mistake me for somebody who likes Go β I don't. I think it was a particularly uninspired effort of 2007+ programming language design.
That said I'm aware that before Oracle got its mittens on Java it was one of the blessed four:
Even when looking at the Closure Library I couldn't shake the impression that it was designed to appeal to the Java developer mindset β but that is just my personal opinion.
So it goes to reason that by the time Oracle acquired Sun MicroSystems in 2010 Google already had built up a substantial legacy Java code base that was too extensive to eliminate.
Google LLC v. Oracle America, Inc.
Now that was largely about Android.
But it has a habit of getting into the headlines:
Sorry, for mistake, didn't mean to be offensive.
My experience with Google is much more recent and by that time Google actively used Java, both in existing and in the new projects.
As for harrasment: case between Google and Oracle is about money between two giant corporations. Despite how it was often represented in media, it was not battle between "good Google" and "greedy Oracle" about Java. And actually didn't presented any danger to Java. Anyway, the battle is over.
As for other cases, I really don't care. From the moment when Oracle made Java open source, their behavior is largely irrelevant - Java will survive regardless from Oracle actions.
The OpenJDK Transition: Things to know and do
More recently: Why Red Hat dumped CentOS for CentOS Stream
There ain't no such thing as a free lunch
Businesses need to get paid for their (commercial) support but the dynamics of how they ensure that they get paid should give one reason for pause.
Is the Oracle vs Google thing that bad? I honestly never considered the corporate aspect, so thanks for this.
Wikipedia: Google LLC v. Oracle America, Inc.
The other thing is that Oracle has a tendency to always look for better ways to fleece its customers β leading to corporate goals like this:
Migration Complete β Amazonβs Consumer Business Just Turned off its Final Oracle Database
"Technologies such as Rust and Go function the same way as Java but they are written in shorter code."
This is just incorrect.
Java is compiled into byte-code and then interpreted by the JVM. Whereas rust is compiled to machine code.
Java itself forces hard OOP, hence the longer Syntax. Rust on the other hand has its lovely trait system.
Please do you research.
This article is horrible to read :)
Keep Coding Y'All π¨π»βπ»
The article deserves its critique, but there's no reason to be mean and call the article "horrible to read". Everyone here is contributes and writes articles for free. Seeing comments like this can even scare other people from writing their own articles. Please be considerate.
I agree with most comments stating this lean article misses the point and there would be much to say around this fairly strange question from some (well also there was an article about 'will Rust replace Python', so there's no limit for puzzling questions).
As much it is right and interesting to wonder which fields Rust will address (like backoffice, embedded IoT, frontends, Linux and more generally OS'es system programming) considering its daring complexity, it appears quite clear to me to note Rust benefits from its youth while Java is quite ossified now. Rust is certainly fast, secure, and modern (with a much potent macro system). Will Rust broadly succeed where academic languages never made it through? No definite answer either way...
Java mainly thrived on backend, Android, and as a cross-OS solution (Eclipse, NetBeans...). Something remarkable and strange is Java never made its way in the browser as a frontend option. Such a void place ECMAScript addressed to such an extend its realm is much beyond now.
From some articles I come to read almost daily, C++, C#, ECMAScript and now TypeScript keep being equipped with many most discussed features like functional, asynchronicity, etc and boilerplate squashing. And yes Kotlin, Go, Swift... are also languages communities discuss much.
About Java? No so, very much not so. Uh? Never heard of modern Java as it is the case for modern C++, latest version of C# or TypeScript. And Rust in this respect as the new kid on the block is part of this heat.
I will not elaborate more on those fields Java was king years ago and now not a strong candidate any longer. Java opened a way and is probably lagging behind now. Nonetheless it has an immense installed based and is present in many prominent industries.
Does Java sound like Cobol to some extend?
I am not sure if community buzz is a very useful metric here. I mean Java is certainly not cutting edge, but liked and used are two very different things. As a Java dev I am obviously biased, but I generally don't get the hate.
With the JVM and all the frameworks/tooling around it, even if it's dying, it will be a viable career option for quite some time still. Certainly long enough for me to pick up something else when the ship really starts sinking. Not everyone works in SV after all.
Thank you for this addition. I fully agree with you. I consider Java as a big player for many years to come before it even faint and become a niche as Cobol or Fortran are now.
My reaction was not about buzz only, it was also as in the job offers and projects coming with many other options along with Java are looming large.
For a job seeker or a anyone wanting to engage in the software industry it would be wrong to assert Java is dying, don't go there (it even an option to consider if you plan to join many reference companies). It is still a very sound option for at least one solid decade to go. I'm sure you'll continue having fun with Java!
Every programming language has its pros and cons and over time becomes suited for certain kind of development. No language replaces any other language ...
Well, if we talk about a great enough time period, most languages will be replaced, at least at the general usage level.
I still hope that JS becomes the browser version of Java bytecode. Any day now!
For the browser we have been stuck on JS, or at least compiling to JS for a while now. With WASM there finally seems an alternative, although currently you still need a bit of JS.
Yes, I don't think Java is going to be replaced
Yes, but without Java, there is no JVM. And especially Kotlin, you really need Java libraries for some things..
Some comments may only be visible to logged-in visitors. Sign in to view all comments.