71
The future of back-end development
(lemm.ee)
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Follow the wormhole through a path of communities !webdev@programming.dev
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.