2cents from an ordinary Java developer

[Jesse Kuhnert]

I think that's all we want. Some way of determining this that seems
fair and logical and doesn't feel like an arbitrary decision being
made. That would be much easier to swallow by the dev community as a
whole than the arbitrary decision path, I'm guessing.

On Wed, Feb 3, 2010 at 9:54 AM, Mark Mahieu <markmahieu at googlemail.com> wrote:
> I suspect it would be terribly difficult to draw useful conclusions from any such exercise.  There are so many variables, and the chance of bias (however unintentional) is huge.
>
> Alex Buckley's request for statistics on existing codebases approaches the question from a different angle, but seems more promising.  Personally, I think it would be good to see a few more responses.
>
> Regards,
>
> Mark
>
>
> On 3 Feb 2010, at 14:23, Jesse Kuhnert wrote:
>
>> If it all comes down to guessing/thinking that it's possible ordinary
>> developers will have issues why doesn't someone(s) just do a small
>> test sampling of devs?
>>
>> Pick a comparable enough language (guess Scala) and grab a few
>> engineers you think would have trouble and record results. There
>> certainly would seem to be enough resources / developers floating
>> around at the corporations people on this list work for to make it
>> worth trying?  Could be that everyone is right and closures will not
>> be understood easily enough,  but without any kind of semi-scientific
>> method for determining this you're still just guessing..
>>
>> On Wed, Feb 3, 2010 at 2:36 AM, Mark Mahieu <markmahieu at googlemail.com> wrote:
>>>
>>> On 3 Feb 2010, at 06:35, Neal Gafter wrote:
>>>>
>>>> The ordinary Java programmers of today are not ordinary programmers
>>>> from a point of view 5-10 years ago.
>>>
>>> Neither is the code they work on.  My, how the boilerplate hath grown...
>>>
>>>
>>>> As our languages change, so does
>>>> our sense of common and ordinary.
>>>>
>>>
>>> That's very true, and in more ways than one.
>>>
>>> 5 years ago the team I was working within contained very few programmers with any real experience using a language other than Java.  About 2 years ago many of them were spending some of their time in Ruby-land *.  As of about a year ago, we have Ruby programmers on the team who have never worked with Java (or they won't admit to having done so, I'm never quite sure).
>>>
>>>
>>> Mark
>>>
>>>
>>> * often their first exposure to lambdas, with "why on earth can't I just write it like that in Java?" being [a polite version of] the typical reaction.
>>>
>>>
>>>
>
>