"Roedy Green" <see_website@[EMAIL PROTECTED]
> wrote in message
news:9csfk39tigm15ls0td1p6v6rvkqfp65ues@[EMAIL PROTECTED]
> On Sat, 24 Nov 2007 08:52:50 GMT, Roedy Green
> <see_website@[EMAIL PROTECTED]
> wrote, quoted or indirectly quoted
> someone who said :
>
>>Presuming these trends continue, where should Java go next?
>
>
> We are also creating larger and more complex programs, with larger
> teams producing them. We need to figure out ways to improve
> co-ordination.
>
Whatever happened to walking over to someone's desk?
Or in the "modern" world of physical disconnect between team members,
Skype/telephone and instant messengers?
> for example
>
> 1. dynamic version control.
> http://mindprod.com/jgloss/project/dynamicversioncontrol.html
> At the least an ability to have a fresh compilation of the latest
> checkins on tap automatically.
>
Got that. CruiseControl (or Bamboo) is your friend
> 2. terser code. Ways of tem****arily hiding code not of interest.
>
Got that. IntelliJ is your friend
> 3. Ways to create and maintain GUI code visually.
>
Got that. IntelliJ is your friend
> 4. formal ways of placing queries and answers for other programmers
> embedded in the docs.
Got that. A simple textfile in the project doc is your friend.
None of which have anything at all to do with the language, they're all
related solely to the tooling you use with it...
Or are you suggesting we turn Java (the language) into something like
Visual
BASIC (the language/IDE/runtime)?
Because if you want that, just download Netbeans and be done with it (or
even better, buy IntelliJ).
It seems your procedures and toolset are wrong and need ammending, rather
than the language. Or maybe you're on a quest to destroy Java by adding
things to it which noone will want except you (just like the guys trying
to
get function pointers, properties, multiple inheritance, and whatnot into
the core language).
|
