|
The views expressed in this article are solely the views of the author and not the owner of this IP address.
== Page Is Irrelevent ==
Is Wikipedia in the business of providing competing product comparisons?
These are two proprietary products produced by competing corporations. The features in both products are subject to change based on the owners goals and marketing decisions without public input. Thus many of the details are volitile and the article will quickly go stale. There are already inaccuracies on both sides of the comparison some due to the age of the article and others intended to skew the article.
The features comparison colors the yes and no values green and red respectively. This is an immediate value judgement on the included of featues. Due to this red/green coloring a minority of the tables of features have more red boxes on the C# side than the Java side. A simple glance at this bias reveals an immediate inference that C# is better than Java, despite many of the features that are not in Java are conscious design decision by Sun/Oracle.
It could be said that Microsoft has taken a kitchen sink approach to language design while Sun/Oracle has taken a more measured approach to feature inclusion. This is implied by the discussion about keyword growth in Java vs C#. So, as is common comparing any two languages in computer science, feature count and quality of features are not relevent to language utility, inferiority, or superiority. Thus the red/green coloring is misleading and at times innaccurate.
Finally, the code samples are also misleading. All the code samples as displayed have a greater line count for Java than the 'equivelent' C# implying Java is more verbose. In the article this is true for multiple reasons. The algorithms are different. In the Input/output section the Java example uses buffered IO while the C# sample does not. The Java implementation uses a superfluous File object constructor on both input and output which is not necessary (Constuctors for FileReader and FileWriter exist with a String argument for a file path like C#). Also to make the IO buffered in the C# example would need a call to a BufferedReader and BufferedWriter constructor to bring the number of constructor calls between the two samples equal.
Similarly, the "Pass by Reference" uses style to increase the line count Java sample. First: The swap method adds a line of whitespace after the temporary variable initialization. Second: A three line comment is added above the main method in the Java example. Third: the output line at the end of the main method is split into two lines in the Java example while being syntactically identical. Finally, even more damning the example is chosen to show the differences in C# and Java while casting the Java in a bad light because it "still" has not changed the value of s. Another equally simple example can be chosen where C# does not produce the results expected.
These are just two of the examples of how code that is contended to be "equal" is used to show disadvantages in Java. There are more.
This page should be scrapped and not rewriten for the reasons stated at the top. If not scrapped is should be rewritten to remove biases noted above.
One last note, I make my living writing C# code.
The views expressed in this article are solely the views of the author and not the owner of this IP address. <span style="font-size: smaller;" class="autosigned">— Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[Special:Contributions/72.37.248.4|72.37.248.4]] ([[User talk:72.37.248.4|talk]]) 02:37, 20 December 2012 (UTC)</span><!-- Template:Unsigned IP --> <!--Autosigned by SineBot-->
| 