What are your opinions on the future of back-end web development? Is the Java ecosystem going to wither away as more modern and better solutions are emerging and maturing?
If so, which language/framework and/or programming paradigm do you think will become the new dominant player and how soon?
Personally I would love to see Rust becoming a new standard, it’s a pleasure to write and has a rapidly growing ecosystem, I don’t think it’s far away from overtaking Java. The biggest hurdle imo is big corporations taking a pretty big risk by choosing a relatively new language that’s harder to learn compared to what has been the standard for decades.
Playing it safe means you minimize surprises and have a very large amount of people that are already experts in the language.
Taking the risk will definitely improve a lot of things given that you find enough people that know or are willing to learn Rust, but it also means that you’re trading off Java flaws with Rust flaws. That’s the case however with every big change, and Java flaws are a good enough reason to make a big change.
Exactly. The only reason Java is remotely tolerable today is because of influences from those ‘fad’ languages. Kotlin and Scala were also fads when they came out, they just got adopted because Java was utter shit at the time. Hell, even Java was a fad at some point in time.
I think a strong argument could be made for the JVM as a whole to be honest, since it encompasses several languages. That being said, I’m not sure I’ve seen a backend written in Kotlin despite how prominent it is for app development.
I worked with really Big Bank who have their whole backend written in kotlin. It was such a great thing to witness because usually financial institutions don’t give a fuck about clean code and modern programming languages.
I’ve been using ktor in a personal project and it’s been a joy; all the familiarity of Spring but with Kotlin first.
Also, I know that Amazon has started to switch some projects to Kotlin, since they’re such a large Java shop: https://aws.amazon.com/blogs/opensource/adopting-kotlin-at-prime-video-for-higher-developer-satisfaction-and-less-code/
Amazon has been adopting a lot of languages in recent years, including writing services in Rust and C# to my knowledge. It’s cool seeing them branch away from Java, although I know that internally they use their own flavor of Java (Corretto).
I can tell you without any shred of doubt that Amazon still standardizes on Java-based frameworks, including Spring, and has absolutely no plans to switch. Each Amazon team is able to pick its own tech stack, but the ones that do not use Java or a JDK-based stack are extremely rare, and more than not are working on specialized applications such as mobile development.
It is branching away from Java, even if it still uses it primarily. Unusually, off the top of my head, I happen to know more .NET developers working there than Java developers, and interestingly they develop one of the services on AWS. I know that there are significantly more Java developers, but I don’t think we are in disagreement that there are projects that don’t use Java.
I’m sorry to tell you, but I assure you it is not. Some small subset of teams uses non-java tech stacks but that’s because they have very particular requirements, such as being android apps or running on Linux devices. The bulk of the company heavily standardized on Java and has no plans to ever move away from it.
First of all AWS is not Amazon.
Secondly, I can tell you for a fact that C# is one of the rarest tech stacks at Amazon. Even Amazon’s internal build system does not support it.
I’m afraid you’re talking about stuff you know close to nothing about.
I’m sorry to tell you, but I assure you it is. Like I said, we both agree that Java is the predominant language, but at Amazon there are services written in Java, TypeScript, C#, and Rust to name a few.
First of all, AWS stands for “Amazon Web Services”. It’s not Amazon? Does Amazon not employ people to work on it? Perhaps you’re thinking of amazon.com?
Amazon’s country-named build system supports building many different languages, including C++, Java, Rust, and yes, teams have even managed to make it work for C# projects. It isn’t a Java build system, it’s a multi-language build system.
I find it funny how every single comment you post includes a personal attack. Since you seem incapable of backing up your own points with anything but insults, you can be the first person on my block list.
lysdexic keeps talking about Amazon but has no clue how it works. Take it from someone who recently worked in AWS. You are right in all your points.
I can also tell you without any shred of doubt, that there are many Amazon teams that absolutely hate Java and would rather build their stack on top of anything else (except PHP, which is rightfully prohibited company wide)
Irrelevant. What matters is what the company uses, not what some guy’s personal taste.
Amazon standardizes on Java. There is no way around this fact.
Yes, some “guy’s” personal taste matters, because if employees hate it, over time they will stop using it. When you get paged at 4AM because some NPE popped up in prod that could be avoided by any sane language you will think twice on the next stack you build. And since when does popularity equal quality?
That’s funny because as a backend Kotlin dev I literally haven’t seen an Android app written in Kotlin (at any of the companies I’ve worked at) but have worked since 2016 with Kotlin on the backend.
Before google announced support for Kotlin the split was massive. Most apps were backend with only a fraction Android. And Kotlin wasn’t even originally built for Android. It only happened to work and then it got popular after someone reported a bug on Android and they fixed it.
It’s nice to see that it’s in use for backend. I personally haven’t seen it, but I always felt like it’d be a good choice for backend development.
Yeah it’s great! We compile it into native code and deploy it as lambdas on aws. It’s actually faster than most nodejs lambdas. I love it!
Scala got adopted? https://insights.stackoverflow.com/trends/?tags=scala%2Cc%23%2Cjava their business model is killing the language
Apparently I used it at its peak. It was the go to language for big data processing at the time
We had developers leave my company because they had to work with scala during 2 -> 3 migration. Everybody hates it now
I never used Scala 3 but was under the impression that the migration wasn’t as bad as Python 2->3 https://lichess.org/@/thibault/blog/lichess--scala-3/y1sbYzJX
This better shows what migration is like https://docs.scala-lang.org/scala3/guides/migration/incompat-syntactic.html
More, new brackets near lambdas, new string formatting, indentiation change. Doesn’t look much, but absolute madness when your team is weak in Scala. Only 1 dev had prior scala experience, but whole team had to be involved in migration of breaking changes in scala syntax behavior and… same for gatling. Also changes in syntax. Mid-level dev left the company because of it, we very soon completely got rid of scala and replaced it with TS and Go. Both languages new to the team, but 0 complaints since February.
This might be your personal opinion but it is not a very informed one, or in touch with reality. Java frameworks such as Spring still dominate the backend ecosystem and some FANGs still standardize their backend development around it.
Read that again. I didn’t mention anything about ecosystem, I said Java, aka the language and JVM. You can patch it up all you want with frameworks, it is still a shit language, had an absolutely useless GC up until Java 9 (20 years into its existence). Though it has gotten slightly less shit in the last couple of years. It is informed from years of working with Java 6 onwards. The fact that I don’t agree with your opinion doesn’t make me less informed.