Jeff Bonwick wrote: > Does it matter? I mean, big picture, is it even worthy of discussion? > > VMware's long-term goal is to become an application platform that > obsoletes all existing operating systems. (Did you know they're > currently developing JVM, Rails, etc that run natively on ESX?) > Linux is trying to eradicate our developer community. Intel and > AMD are trying to make SPARC completely irrelevant. And we're > arguing about /usr/benchmarks vs. /opt/benchmarks? > > I'm all for defending architectural purity when there's some > fundamental principle at stake. If there's one here, please > enlighten me. > > Jeff > To me, the issue is namespace preservation. Benchmarks seem to not have unique names in many instances. Sure, we can just wait until we run into this problem, but by then, it will a 10x harder problem to deal with.
So, I think this is actually about saving money. FRAM oil filters ran an ad for many years with the tag line: of "You can pay me now (for the filter) or of pay me later (an overhaul)". You get the idea. The only significant issue is "to bin, or not to bin". I the choice is "not to bin", then somebody needs to make a choice as to where. If its a new place, there should be a semantic definition of the new place. This should take a couple of hours to accomplish. - jek3
