Mailing-List: contact dev-help@wicket.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@wicket.apache.org
Received-SPF: pass (nike.apache.org: domain of eelco.hillenius@gmail.com
 designates 209.85.210.191 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        b=uWrbfTU7A0VTrrRrNYqoxmsoDgMDcpuUmNnnJJkRTX6Nssyb3lmhw99qDqOWKw0lHN
         H/lODfAxR9FUJ9JFKiPz6kZAbyTwizOyClFgzYWEcy21UOR+woPHIPDbHsjt13YrjBai
         Y2uion1qcygNKZUqr8PvbjjEDS7hjjZ07iE04=
MIME-Version: 1.0
In-Reply-To: <109027740910040645p1ebf8551x21a301b7b1c7ca50@mail.gmail.com>
References: <23eb48360910021528w65e89314u94ebc65c11e9e0df@mail.gmail.com>
	<4AC88D32.2030704@grons.nl> <1254662366.9888.43.camel@martin>
	<109027740910040645p1ebf8551x21a301b7b1c7ca50@mail.gmail.com>
From: Eelco Hillenius <eelco.hillenius@gmail.com>
Date: Sun, 4 Oct 2009 15:14:57 -0700
Message-ID: <ceb609d80910041514q1d446baclc6a38a554f04e825@mail.gmail.com>
Subject: Re: taking the I out of Interface
To: dev@wicket.apache.org
Content-Type: text/plain; charset=ISO-8859-1

I just want to get off my chest that it is amazing to me we all make
such a big deal out of that "I" being there. It's been there forever,
and with previous discussions we always concluded to leave it in
there. I never liked the code format we're using (curly braces on the
next line), but heck even though Wicket is the only project I've ever
worked on (as far as I can remember) where I used that, it's not
something to lose sleep over. Same with the I, I like it, but I'd be
fine with any alternative. More problematic to me is that we're going
to break a lot of code - including code printed on dead trees - over
it while there is absolutely no benefit other than a superficial one,
and as you can see from the replies in the thread, it's not even
universally thought of as better. And I think that some are a bit too
quick to trivialize that. Breaks, even little ones are annoying and
imho only justifyable when there's a clear benefit to doing that. But
this is plain nitpicking to me.

I wouldn't give this a blocking vote, even if I had been more active
in the last year, but I'd like to ask everyone to not take even little
API breaks too lightly.

Eelco