3 ms·
You can do anything in anything. Everything boils down to trade offs for the problem or company at hand. I can say with Java and .NET shops, it's usually becau
by brightball 7y ago
You can do anything in anything. Everything boils down to trade offs for the problem or company at hand.
I can say with Java and .NET shops, it's usually because the company has heavily invested in Java and .NET infrastructure, process, automation, tooling, monitoring, etc. If there are certifications involved, I also know for a fact that Microsoft feeds big discounts on expensive products (SQL Server) depending on how many employees you have with Microsoft Certifications.
It becomes a self feeding system. You're already invested so much in the stack that the choice of using something else is far more complicated than language comparisons. It's one of the reasons that there are so many language options available that run on the JVM that can take advantage of all of that investment without forcing the devs to write raw Java (Groovy, Scala, Clojure, Kotlin, etc).
- RhodesianHunter 7y agoIt isn't just the company's heavy investment, it is the community's. The availability of good, tested, performant OSS libraries available in Java is unparalelled. People talk about languages like Python being "faster" to develop in because they're easier to write. This is true until you need a solid concurrency friendly loading cache or a DB connection pool that works at scale and in Java that's just adding a dependency that you know you can trust.
- brightball 7y agoI didn’t expand on it, but that’s what I meant by trade offs for the problem at hand. Agreed.