[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [dist-obj] B-A-I-T :) (was: Re: [dist-obj] [Longish] ... )
David McCusker writes:
> However, they over-commited to the big picture, and the explanation
> of choices involved uses the phrase "performance transparency"
> which was very interesting in this context. This phrase refers to
> code having a nature allowing a developer to estimate runtime costs
> by looking at the source code.
Not really a noble goal. I don't mind writing expensive code
cheaply. Who knows? I might get away with it here and there.
> In practice I see developers falling in two buckets with small overlap:
> (A) folks good at low level languages who make good use of performance
> transparency, and (B) folks good at high level languages who don't.
I see a lot of (C), people concerned with nitty gritty performance
issues when some bigger picture is swamping everything else.
I also see a lot of (D), people enamored with technology they don't
really need in all cases. Even distributed systems sometimes.
> Even worse, one can grow systems no one understands at all. Folks might
> be surprised to realize how many systems in the world today operate with
> no one at all grasping how they are effective.
Like Internet bubbles? 8*)
Patrick Logan mailto:firstname.lastname@example.org
Voice 503-533-3365 Fax 503-533-3220
Gemstone Systems, Inc http://www.gemstone.com
To manage your subscription, mailto:email@example.com
Archives, FAQ, etc. http://www.distributedcoalition.org/mailing_lists/