Good point Miroslav, the bulk of our day is spent getting Maven to behave, dissecting Spring stacktraces etc. - and that is a BIG different from what programmers dealt with a decade ago. However having said that, recent language evolution caters to internal/ embedded DSL friendliness to try and bridge that. I.e. LINQ is a pretty darn nice way to be able to write type-safe queries as first class constructs in the language, with all the support an IDE can give you. So I think language vs. API is going to keep blurring.
On Sep 30, 3:20 am, Miroslav Pokorny <[email protected]> wrote: > There is too much trivial opinion and not enough solid real meaningful > facts. I dont understand why people love a certain language so much and > forget that we spend more time working with libraries therefore they are the > most significant aspect of our work. Having the best most > expressive/powerful language is great but a small factor when one considers > the effort required to work with libraries. I find poor documentation or > crappy exception messages more of a worry than the first class constructs of > a language. -- 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.
