For further consideration, round 2

[Ruslan Shevchenko]

Good day.
Some random notes about including/excluding proposal to/from final draft.
Of course, from my part of elephant.
// Knowing, that my and Joe Darcy opinions usually opposite, you can
// inverse my suggestions and receive final results ;)


1. Logically a combined proposal for better integral literals:
 Including this to final draft will make changes to language hightly
alogical: if integers than why not strings ?
One difference - that for strings we have group of users (database
developers), for which live without new strings is a big pain; for
integers - not.
But reverse usability looks strange to be acceptable criteria.
So, my vote - does not include new integer literals.

2. Improved Type Inference for Generic Instance Creation.
 Ohh. Sorry, but I must say, that choosing such variant of limited type
inference over 'auto' proposal will speed-up process of switching
developers from java to less verbose languages: java become not 'archaic
because infrequently updated', but 'archaic by design'.
>From other side - this is better than nothing. So, better include.

3. Language support for JSR 292. Must be. (Also, with reasons from
previous item, main value of Java will  be 'good JVM C/assembler')

4. Automatic Resource Management. Must be.

5. Large arrays. Knowing (3): better include.

6,7 (Elvis and Other Null-Safe Operators,  Indexing access syntax for
Lists and Maps)
  I have no special opinion. I. e. including or excluding such proposal, I
think, globally will change nothing.

8,9, Strings in switch, Collection Literals. In principle the same as
(6,7) but effects from those proposal is less then listed for previous
items.

10. Simplified Varargs Method Invocation.  I guess this is
'maintance-like' proposal. Better include.

That's all.
 Regards !