What is the reason for the prevalent usage of Java (along with Spring MVC) in major IT companies and websites like Google, Mail, Amazon, and PayPal (stats: https://en.wikipedia.org/wiki/Programming_languages_used_in_most_popular_websites) ?
Is there something lacking in Asp.net when compared to Java?

The prevalent usage of Java, along with Spring MVC, in major IT companies and websites can be attributed to several factors. Firstly, Java is a versatile and widely adopted programming language with a large ecosystem of frameworks and libraries. It offers a well-established and mature development environment, making it easier for companies to find developers and maintain their codebases. Additionally, Java's architecture-neutral design allows developers to write code once and run it anywhere, making it suitable for building scalable and platform-independent applications.

While Java has gained popularity in web development, it does not necessarily imply that ASP.NET or any other technology is lacking. Different companies and development teams have different preferences and requirements when choosing their tech stack. ASP.NET, Microsoft's web development framework, also has its strengths, such as seamless integration with other Microsoft products and technologies, and strong support for developing enterprise-grade applications.

points to consider in the comparison between Java (with Spring MVC) and ASP.NET:

1. Community and Support: Both Java and ASP.NET have large and active communities, providing extensive resources, dоcumentation, and support for developers. However, Java's community is generally considered larger and more diverse, potentially offering a wider range of libraries, tools, and frameworks.

2. Cross-platform Compatibility: Java's "write once, run anywhere" mantra allows applications to be developed on one platform and deployed on multiple platforms without significant modifications. ASP.NET, on the other hand, is primarily Windows-based and requires additional effort to run on non-Windows systems.

3. Performance: Both Java and ASP.NET are capable of delivering high-performance web applications. However, Java is often touted for its scalability, asynchronous capabilities, and strong performance under heavy loads.

4. Integration with Existing Systems: If an organization already has a significant investment in Microsoft technologies, such as SQL Server or Active Directory, ASP.NET may offer smoother integration and interoperability with these systems. Similarly, Java's open-source nature provides flexibility in integrating with a wide range of third-party systems and tools.

5. Development Tools and IDEs: Both Java and ASP.NET provide robust development tools and integrated development environments (IDEs) like Eclipse, IntelliJ IDEA, Visual Studio, and Visual Studio Code. The choice of IDE may depend on personal preference and familiarity.

and:

1. Language Paradigm: Java is an object-oriented programming language, while ASP.NET supports multiple languages, including C#. The choice between these paradigms depends on the development team's familiarity and preferences.

2. Runtime and Virtual Machine: Java runs on the Java Virtual Machine (JVM), which provides benefits such as automatic memory management, platform independence, and strong security features. ASP.NET, on the other hand, relies on the .NET Framework or the newer .NET Core runtime, which provide similar benefits and are optimized for Windows environments.

3. Development Speed and Productivity: ASP.NET is often praised for its developer-friendly features, such as drag-and-drop controls, a rich set of libraries, and built-in support for data binding. It allows developers to quickly build web applications and take advantage of the extensive Microsoft ecosystem. Java, with Spring MVC, also offers productivity-enhancing features, but it might require more configuration and setup in comparison.

4. Enterprise Support: Java and Spring MVC have a strong foothold in the enterprise world, with a history of being used in large-scale projects. This can be attributed to the robustness, stability, and resilience of the Java ecosystem, as well as the availability of enterprise-level tools and frameworks.

5. Community Trends: While Java has a longer history and larger community overall, ASP.NET has gained significant popularity in recent years, especially with the introduction of .NET Core. The choice between these technologies can depend on the specific trends and demands within the development community.

At present, C# (asp.net) possesses several advantages compared to what Java offers in terms of language convenience and syntax. That is indeed true!

The predicament lies in the fact that Java emerged earlier and was open for use on Linux. Consequently, a vast array of unique solutions were developed specifically for Java servers, which are presently utilized by top teams (one can consider what hadup is, for instance). As a result, companies either failed to perceive the rationale behind rewriting everything in C#, given that they had already established Java builds, or they simply did not wish to invest time into duplicating what already existed in Java.

Due to this very reason, Microsoft has recently initiated active collaboration with Linux and is proudly expressing their affinity towards it.

Regarding the current status, numerous companies have now started implementing C# (asp.net) for building their systems - frequently, these are new ventures like Dodo Pizza. However, the old folks still remain steadfastly loyal to Java and refuse to transition.

There are numerous speculations to be made, just like I once pondered about this very question.

1) Every major corporation, including Google, started off as a small entity. Similarly, the availability of .net was limited in the past.
 
2) The expenses associated with software infrastructure such as IIS, MSSQL, and VS can be significant for companies.

3) Moreover, due to the relatively lower distribution of .net, there is a scarcity of qualified specialists, resulting in higher salaries for developers.

4) In regards to point 3, it becomes more challenging to find skilled workers. If we consider universities, how many actually teach the fundamental .net stack? I recall observing programs from around 15-20 universities across different countries, and usually .net is treated as an optional module. Perhaps I could be mistaken, but in my entire life, I have only come across a mention of .net core 1-2 times.

If one carefully thinks about it, there are plenty more aspects that can be added to the discussion.