Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

11
  • 6
    Unfortunately a by-product of Java's commendable aim of simplicity in their design and syntax made it very easy to learn at a level where you can wreak havoc without the tinyest ounce of understanding. Nobody would do such a thing in assembly for example, because you wouldn't get anywhere without understanding the ins and outs of it. Commented Feb 21, 2011 at 22:18
  • 3
    @biziclop: Are you suggesting that there's no such thing as badly written assembly? You can write bad code in any language. Commented Feb 22, 2011 at 8:20
  • 2
    no, he (if I understand him correctly) states that it's easier to write bad code in Java that actually compiles and is functionally correct compared to doing the same in Assembler. Thus bad Assembler code is less likely to end up in the maintenance queue, as it never reaches production. Commented Feb 22, 2011 at 9:48
  • 2
    There's lots of poor Java about. But compared to C it is absolute bliss. Commented Mar 29, 2011 at 12:22
  • 6
    Employer: "I have some very poorly written C++ and some very poorly written C#. Which do you want to work on?". No brainer, give me the C# Commented Mar 29, 2011 at 15:09