101 دلیل برای برتری Java نسبت به .NET

101 Reasons Why Java is Better than .NET (Reloaded)

The original edition was put together using a blogging system, this edition is now based on a Wiki system. Hopefully, the comments and contributions will be richer this time.

The list is structured such that all 101 entries can be viewed on a single page (unlike the original!). Each entry would be accompanied by a "sound bite" that bests captures the intent of the entry (if you got a good one, please let me know!). Each entry is also a link that you can navigate to examine more details and supporting information. At this time there is no particularly reason for the ordering and that will change at a later date (so please don’t cite the entries number when you make an external comment!).

For an easy to remember url to link to this list and all future editions use 101.manageability.org . Feel free to post this url in response to articles and posts falsely promoting the benefits of .NET.

Finally, for those who unfortunately have legacy .NET deployments, here a series of articles that will help you migrate to a superior Java platform .

  1. Public Domain APIs – Any Java public apis are part of the public domain, .NET apis are proprietary and can open the door to a law suit.
  2. Standard Library Source Code Availability – Java source code for the core libraries are available in every J2SDK distribution, .NET sources can only be seen by resorting to illegal means.
  3. dotNet Purity Is A Myth – Java promotes 100% pure Java libraries, for .NET purity is nothing more than a myth.
  4. 75% Of Enterprise Software Development – Avoid becoming one of the 25% of "use-less" employees.
  5. Preferred Platform for Implementing WebServices – Despite billions spent by Microsoft in marketing, surveys continue to reveal that Java is the preferred platform when it comes to Web Services.
  6. Superior Platform for Web Development – ASP.NET is a poorly designed and crippled framework as compared to the richness of frameworks found in Java.
  7. Write Stored Procedures using Java – Most relational databases support writing of stored procedures in the Java language. There has yet to be a production release of a database that supports any .NET languages.
  8. An Abundance of Experienced Practitioners – Nobody seems to know how to write .NET programs well and that’s giving .NET a bad name! A pretty lame excuse I must say!
  9. Supportive Open Source Communities – Open Source communities that support distributed development are a plenty in the Java world.
  10. Proven Security – 2 Years after Trust Worthy initiative is launched and we collectively lose $55 billion last year.
  11. No Lizard Brain – .NET programmers continue to struggle with the complexities of a hybrid managed/unmanaged environment.
  12. More Languages – The JVM is more "common" than the CLR.
  13. Smaller Runtime Download – You can’t run your app if you don’t have the runtime.
  14. No Mandatory Upgrade Fees – 3 things a Microsoft shop can’t avoid: Death, Taxes and License 6.
  15. More Vendor Choices – .Net is a marketing program. Java is a Market.
  16. Industrial Strength Collection Classes – The .Net libraries look like they were designed by high-school students, First year CompSci? students at best.
  17. FutureProof – The way to ensure your return on investment (i.e. ROI) is that your choice of platform doesn’t get obsolete in 5 or even 10 years. Avoid the Microsoft upgrade treadmill!
  18. Larger Talent Pool – Majority of Universities not only teach but require knowledge of Java. That’s a big talent pool that you need to consider before you off-shore your project to a different time-zone.
  19. More Contributions From Researchers – Research institutions and universities have consistently provided innovative research not only built on top of Java but also contributing to Java.
  20. US Government Approved – Guess where the billions of dollars spent on the U.S. government’s IT renovation is going to?
  21. NoEvilTypeCoercion – Some C++ constructs are meant to be entombed forever, .NET resurrects them with disastrous consquences.
  22. More Mature And Robust O/R Mapping – You can’t beat the wealth of O/R mapping solutions found in Java.
  23. Superior Coding Tools – Like having your own personal Java fairy dancing through your code, anticipating your every thought and keystroke.
  24. Sane Coding Conventions – I don’t know what’s worse Hungarian notation or .NET coding conventions.
  25. Higher Paying Jobs – Somehow you’ve got to afford those skyrocketing housing prices don’t you?
  26. Favored for Implementing P2P – Gnutella and JXTA, anything else legally more pervasive?
  27. PureJavaRDMS – Can’t beat the ease of installation when the RDMS is Java based and packaged with the application in a .zip file.
  28. More Exception Handling Options – .NET has no analog to the throws clause in method signatures.
  29. Better Structured Diagramming Frameworks – When going beyond forms and windows, Java can’t be beat.
  30. Reusable Open Source IDE Frameworks – Why re-invent the wheel? Start building your killer GUI application on top of killer IDE frameworks.
  31. RobustParserGenerators – Want to build a new language, well you’ll need some robust parser building tools.
  32. AspectOrientedProgramming – The next advance in modular software development, get a head start by using Java.
  33. PureJavaWebServers – Customizations and extensions are easier in a web container that’s built using the same language as applications. Furthermore, managed environments support better reliability and security.
  34. OpenSourceJavaCompilers – Your tools have got to be able to parse the code before it has any chance in understanding it.
  35. Distributed Caching – Sometimes embarassingly parallel applications aren’t the only things that you need to scale.
  36. MultipleReliableMessagingChoices – Java provides more choices for the backbone that integrates the Enterprise.
  37. Faster Development Turnaround – Incremental compilation is unavailable in the .NET environment.
  38. Lightweight Persistence – Sometimes a relational database (RDMS) has too big a footprint.
  39. Open Community Process – How does one contribute to the specification of standards?
  40. Hardware Accelerators – Performance boosting hardware.
  41. More Flexible Licensing Options – Ultimate flexibility in licensing.
  42. EmbeddedDevices – Java inside small packages.
  43. WholeProgramOptimization – Please sir may I have a linker?
  44. Comprehensive RDMS Driver Support – Can you find a ADO.NET driver for an open source database?
  45. NetworkingSupport – Why is MSN managed by a Java based tool?
  46. Garbage Collect Classes – The only way to unload MSIL code is to unload an entire application domain.
  47. Better GUI Framework – Why isn’t VS.NET written in a .NET language?
  48. Standardized Portal Frameworks – Standardized ""Integration at the glass"".
  49. RunInIntepreterMode – ""We’re just not optimized for interpreting""
  50. SuperiorBuildEnvironments – A .NET practitioner’s concept of a build is F7.
  51. MorePDASupport – Why limit oneself to a single PDA brand?
  52. OpenTechnologyRoadmap – .NET is like a five year plan in the former USSR: You know it doesn’t actually make sense or help anything, but if you live under it, you’re certainly not going to say anything negative about it.
  53. JavaCard – JavaCards? are becomming the preferred method of keeping tabs on your citizenry or customers. If Microsoft ever co-opts this technology then "1984" will become more than just a paperback novel.
  54. Complete Open Source Stack – Open Source code visibility spanning all layers of an application.
  55. NonStopServers – .NET not fault-tolerant enough for Hewlett-Packard-Compaq?
  56. Out Of This World – Java runs on other planets, .NET has yet to leave Terra Firma.
  57. Better Unit Testing Support – More extensions and comprehensive IDE support
  58. More Identity Management Solutions – Can you trust Microsoft to keeping your customer’s identity secure and available?
  59. Most UML Tools Implement In Java – Ever wonder why the best UML tools are implemented in Java?
  60. More R&D On Intelligent Agents – Java is the preferred implementation platform for Intelligent Agents.
  61. Easy Rich Client Deployment – No-Touch development was shaky.
  62. Lower Cost for Massively Parallel Systems – How much does it cost to deploy a .NET application on a platform with 10,000 servers like google?
  63. More Profilers – Profilers mitigate the risk of not finding the root cause of show stopping bugs.

دیدگاهتان را بنویسید

نشانی ایمیل شما منتشر نخواهد شد. بخش‌های موردنیاز علامت‌گذاری شده‌اند *

اجرا شده توسط: همیار وردپرس