5 ms·

Are there still any reasons why one should choose Java instead of .Net for new developments?

• hocuspocus 10y ago
  The JVM ecosystem is vastly richer.
• avalchev 10y ago
  :) Probably because Java runs without problems on Windows and *IX platforms without major problems.
  • wolfgke 10y ago
    > Probably because Java runs without problems on Windows and IX platforms without major problems. Probably because Java runs without problems on (Windows) and (IX platforms without major problems). FTFY ;-)
    • sixbrx 10y ago
      I've been using Java on Linux in production for more than 7 years and have never had any problems associated with the OS choice.
      • astrodust 10y ago
        There are operating systems with "major problems" out there. Linux isn't the only *IX.
• fusiongyro 10y ago
  One reason might be you have a team of Java developers. I personally acknowledge that C# is a nicer language, but on Macs and Linux machines I have not had a great experience using it so far. I think if you try it today, you're basically an early adopter. If you're going to be an early adopter, the barn doors are wide open and I'm going to make serious consideration of Python, Haskell or Go.
• rajeshp1986 10y ago
  web programming in C# is not very good. Although I like C# as a language. I hate ASP.NET and the way it is built. Java has much better support for writing web applications and tons of open source libraries.
  • jklehm 10y ago
    There are alternatives, I like this one: http://nancyfx.org/ http://nancyfx.org/
    • norea-armozel 10y ago
      I definitely love Nancy since it's basically Sinatra for C# (IIRC Nancy was inspired by Sinatra).
• twblalock 10y ago
  Cross-platform .Net is not as good as cross-platform Java/JVM. It's getting better, but it's not there yet, and it's currently a very confusing mishmash of concepts and implementations. I suspect it is also difficult to find people who are deeply familiar with it, due to its recency.
• sk5t 10y ago
  There are many, many more good libraries for Java in Maven Central than for .NET in Nuget. OS independence, if not quite platform independence, has informed much of those libraries' development. Maven, love it or hate it, can do a staggering number of things, some of them very useful. JAX-RS servers and clients are more robust IME on Java. (Just try to find a capable path+querystring builder for .NET.) JDBC is still the gold standard for database connectivity.
  • revelation 10y ago
    Maven, where your build script is actually declarative XML that might or might not run. Maven, which spends a minute contacting random servers all over the world only to tell you there is a closing tag missing. I still have a repository where Surefire (hah) refuses to run any tests. Impossible to debug. No, that pile won't be missed.
    • pjmlp 10y ago
      I will rather take Maven a full day over a few seconds with Gradle.
      • vorg 10y ago
        Since Gradle 3, Kotlin is the preferred language for writing build scripts and addins, rather than just Apache Groovy. If you use Kotlin instead of Java for your Android coding, you can use the same language for writing your build scripts as you do for your system code.
  • jongalloway2 10y ago
    Curious what you're looking for in a path+querystring builder. For ASP.NET controllers, I'd use attribute routing's URL generation: https://docs.microsoft.com/en-us/aspnet/core/mvc/controllers/routing#url-generation https://docs.microsoft.com/en-us/aspnet/core/mvc/controllers... If you want a separate library for use outside of ASP.NET, and you want something more sophisticated than UriBuilder, there are several out there. I've used Superscribe in the past, but I just looked around and Flurl looks pretty neat: http://tmenier.github.io/Flurl/ http://tmenier.github.io/Flurl/
• edko 10y ago
  The JVM: it is not only Java than runs on it, but Scala, Clojure, Ceylon, etc. Although many of these languages support other compilation targets (JavaScript, for example), the JVM is always their main and most powerful platform.