4 ms·

Look at the code, Java like, no? But a lot nicer.

by puppetmaster3 13y ago

aeonsky 13y ago
So you want Oracle to include a "shared" and "auto" keywords and break millions of programs?
- grogenaut 13y ago
  Yes, Yes I do. And as for backward compatibility, they already did. I love the myth that java never broke backwards compatibility. Bytecode maybe (), they definitely broke syntax compatiblity. : The various xml parsers and other library thrash really do break backwards bytecode compatiblity.
  - laureny 13y ago
    > I love the myth that java never broke backwards compatibility. Bytecode maybe (), they definitely broke syntax compatiblity. Proof?
    - mhixson 13y ago
      If by "syntax compatibility" he means code that compiles in one version does not compile is another, that's definitely true. Name collisions with the new default methods in Java 8 are one source. If your Comparator-implementing class has a method "void reverseOrder()", that will no longer compile. Here's a couple of recent examples the Guava authors have fixed. Fortunately they were in internals and not their public API, so users won't care. https://code.google.com/p/guava-libraries/source/detail?r=7de3cbca3854ae0d9e9f7973a8f3cfe855a2407a https://code.google.com/p/guava-libraries/source/detail?r=7d... https://code.google.com/p/guava-libraries/source/detail?r=257148b2901c8b8ec1b06d9c10804300ac3d06d0 https://code.google.com/p/guava-libraries/source/detail?r=25...
      - laureny 13y ago
        This happens for all languages and is not usually considered as "a language breaking backward compatibility", it's purely a library concern. What is meant by "breaking backward compatibility" is when the grammar is altered in a way that makes existing sources no longer compile.
    - grogenaut 13y ago
      enum
laureny 13y ago
I don't know if you're just being naïve or if you have absolutely no clue about language design. In case it's the former, "a lot nicer" is subjective, so it carries no weight in the discussion. If the latter... well, go read a few books on compiler design and language theory.
- puppetmaster3 13y ago
  Yes, insult away. You do know D the language was written by compiler expert, right - if you had a point or just insult.
  - aeonsky 13y ago
    If you mean the D language was designed by a compiler expert, then it is as irrelevant as a house designed by a plumber. I don't know, I heard talks by James Gosling and he is much of an expert as anybody.
  - laureny 13y ago
    I was not questioning Andrei's skills, only yours.
    - puppetmaster3 13y ago
      I'd like to point out that you acting like a jerk does not make you look more competent. Java has a reputation of a bad community, and you just underline it here.

Look at the code, Java like, no? But a lot nicer.

aeonsky 13y ago

So you want Oracle to include a "shared" and "auto" keywords and break millions of programs?

grogenaut 13y ago
Yes, Yes I do. And as for backward compatibility, they already did. I love the myth that java never broke backwards compatibility. Bytecode maybe (), they definitely broke syntax compatiblity. : The various xml parsers and other library thrash really do break backwards bytecode compatiblity.
- laureny 13y ago
  > I love the myth that java never broke backwards compatibility. Bytecode maybe (), they definitely broke syntax compatiblity. Proof?
  - mhixson 13y ago
    If by "syntax compatibility" he means code that compiles in one version does not compile is another, that's definitely true. Name collisions with the new default methods in Java 8 are one source. If your Comparator-implementing class has a method "void reverseOrder()", that will no longer compile. Here's a couple of recent examples the Guava authors have fixed. Fortunately they were in internals and not their public API, so users won't care. https://code.google.com/p/guava-libraries/source/detail?r=7de3cbca3854ae0d9e9f7973a8f3cfe855a2407a https://code.google.com/p/guava-libraries/source/detail?r=7d... https://code.google.com/p/guava-libraries/source/detail?r=257148b2901c8b8ec1b06d9c10804300ac3d06d0 https://code.google.com/p/guava-libraries/source/detail?r=25...
    - laureny 13y ago
      This happens for all languages and is not usually considered as "a language breaking backward compatibility", it's purely a library concern. What is meant by "breaking backward compatibility" is when the grammar is altered in a way that makes existing sources no longer compile.
  - grogenaut 13y ago
    enum

laureny 13y ago

I don't know if you're just being naïve or if you have absolutely no clue about language design. In case it's the former, "a lot nicer" is subjective, so it carries no weight in the discussion. If the latter... well, go read a few books on compiler design and language theory.

puppetmaster3 13y ago
Yes, insult away. You do know D the language was written by compiler expert, right - if you had a point or just insult.
- aeonsky 13y ago
  If you mean the D language was designed by a compiler expert, then it is as irrelevant as a house designed by a plumber. I don't know, I heard talks by James Gosling and he is much of an expert as anybody.
- laureny 13y ago
  I was not questioning Andrei's skills, only yours.
  - puppetmaster3 13y ago
    I'd like to point out that you acting like a jerk does not make you look more competent. Java has a reputation of a bad community, and you just underline it here.