Please enlighten me, what part of "should language/library choice be in the
hands of developers or management?" has been previously covered?
Quote me, or anyone else, please...

Read back of that email again - I'm not pushing an agenda, or praising any
particular language, nor am I criticising any.  If I appear to be doing so,
then please point out the precise phrase that caused you such offence.

Pay attention to the questions - what is the fundamental difference between
choosing a library and choosing a language? Where should the balance lie
between devs and managers?

I make a perfectly reasonable attempt to get some group feeling on issues
that are becoming increasingly relevant, yet receive a hostile and negative
response. Why?  How is this in any way a threat to you or your interests?


On 5 October 2010 11:52, Reinier Zwitserloot <[email protected]> wrote:

> Tired of Kevin's bazillion attempt to rehash the same old discussion,
> even after Dick asked for some rest? Chrome user?
>
> Have no fear! This plugin will hide everything he writes:
> http://dl.dropbox.com/u/368812/HideKW.crx
>
> You can uninstall it from the extensions page (Window - Extensions).
>
> NB: Credit goes to Casper Bang. I merely changed a name.
>
> On Oct 5, 10:59 am, Kevin Wright <[email protected]> wrote:
> > Given the range of alternate languages available on the Java platform,
> and
> > the quality of tooling for these, it now seems reasonable that developers
> > could have more freedom to choose the language they work with based on
> their
> > needs:
> >
> > e.g.
> > groovy for small in-house apps needed quickly
> > jruby for web development
> > scala/clojure for financial work
> > etc.
> >
> > By targeting the JVM, many traditional concerns over changing languages
> take
> > on far less significance; such as the need for a new infrastructure, lack
> of
> > in-house operations knowledge and integration with an existing codebase.
> >
> > With the agile and software craftsmanship movements already empowering
> > develops to make more decisions over process and planning (and to take
> > responsibility for these), does it now make sense to also put more
> control
> > over the choice of language into the hands of the people who will
> actually
> > be using it?
> >
> > Of course, there will be management concerns.  It's important to be able
> to
> > hire future developers, and fragmentation could occur if multiple teams
> each
> > chose a different language.  On the other hand, are these
> > considerations fundamentally different when choosing libraries such as
> > hibernate, spring, lambdaj or lombok, or when choosing testng in
> preference
> > to lombok?  and is code reuse in many organisations really high enough
> that
> > you can't already claim the codebases of different projects are
> fragmented?
> >  In truth, is the suffering all that great where we *already* use
> different
> > languages for parts of a system (SQL and javascript anyone...)?
> >
> > Where is the balance here?  Is it really still acceptable, in this day
> and
> > age, for management to mandate that "though shalt use Java, and only
> Java"?
> >
> > --
> > Kevin Wright
> >
> > mail / gtalk / msn : [email protected]
> > pulse / skype: kev.lee.wright
> > twitter: @thecoda
>
> --
> You received this message because you are subscribed to the Google Groups
> "The Java Posse" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<javaposse%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/javaposse?hl=en.
>
>


-- 
Kevin Wright

mail / gtalk / msn : [email protected]
pulse / skype: kev.lee.wright
twitter: @thecoda

-- 
You received this message because you are subscribed to the Google Groups "The 
Java Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/javaposse?hl=en.

Reply via email to