[squeak-dev] The Trunk: Kernel-cmm.757.mcz

Ken G. Brown kbrown at mac.com
Sat May 4 23:18:58 UTC 2013


Since we are apparently bike shedding, I guess perhaps it's time for my contribution. What about #beforeNow and #afterNow, or #inThePast and #inTheFuture?
#fromNow could mean either direction I suppose and is therefore somewhat ambiguous. 

Ken,
from my iPhone

On 2013-05-04, at 17:10, Chris Muller <asqueaker at gmail.com> wrote:

>> Well, no, but English has a habit (as in the thing that nuns wear) of
>> overloading names. Put the boot into your boots, and put them in my
>> car's boot. Lead by example, with those lead boots. But we still
>> manage to make sense of it.
>> 
>> And hence, and henceforth, "hence" will remain "in the future" and "therefore".
> 
> (I enjoyed our Saturday afternoon bikeshed too, just one more back at ya!)
> 
> I have no disagreement here.  But a good and common way to make
> decisions is to keep a "scorecard" and, at least for the round of
> Ambiguity, fromNow won.  You point out that ambiguity is the nature of
> English, which I totally agree with, but that does not change the
> scorecard of that "round" which rates less ambiguity as better than
> more.
> 
> I have no general disagreement with the abstracts Colin said on his
> soapbox about naming either, it's just that the abstracts weren't tied
> in to the concrete to help us understand _why_ hence is better.  Just
> assertions that it is.  To continue with the UFC analogy, the
> decisions are made by evaluating the scorecard, not necessarily by the
> fighter who raised his arms in victory the moment after the final bell
> sounded.  :)
> 
> Having said that, a happy and amicable Colin is important to us all,
> so there is a point for #hence.  :)
> 
> 
>> 
>> frank
>> 
>> (I do love a good bikeshed.)
>> 
>>>  is not describing "a point in
>>> 
> 


More information about the Squeak-dev mailing list