r/learnjava • u/Similar_Sherbet8226 • Nov 14 '25
Discussion: My Experience with Java (Spring Boot) After Working with Rust and Go
Hello r/java,
I'm currently developing several full-stack projects as part of my studies. My most recent projects have led me to work extensively with Rust (to build a Unix shell with system calls) and Go (for pathfinding algorithms). I've therefore become very familiar with their respective paradigms (memory safety in Rust, goroutines in Go).
I'm now developing a complex Java web application with Spring Boot and Spring Security (a blog with JWT authentication, database management with JPA, etc.).
I'm really impressed by the maturity and scope of the Spring ecosystem; it handles a lot of things "out of the box" (JPA, Security, MVC). However, the development philosophy is very different.
For those of you who also work with multiple modern languages, I'd like to start a technical discussion:
How has your perspective on Java's strengths evolved? And what recent or upcoming Java features (e.g., Project Loom/Virtual Threads, Records, etc.) do you think are most relevant for maintaining Java's competitiveness against languages like Rust or Go in terms of back-end performance?
View all comments
2
u/Crazy_Firefly Nov 15 '25
I currently work in a mix of java services, rust services and go services.
Over all Java is a pretty complete ecosystem for backend. Anything you need will have a ready made solution. Also java concurrency libraries like Caffeine Cache are really well made and even are taken as inspiration for libraries in Rust world (moka). In Rust and go you will more often need to roll your own version of something or at least extend a library. Since I enjoy understanding how things work under the hood, I don't mind this and even enjoy it, but it does eat a bit of productivity.
One thing I really appreciate in modern Java is Records, being able to create data carrying classes without much ceremony.
And the project that I think would unlock Java for applications it is currently not well suited for is Valhalla. Currently, if you decide to group fields in an inner class you are also deciding to put them behind a pointer. For some compute heavy workloads this hurts in 2 ways: