Re: metalink still unuseable the 2nd day ...
Date: Thu, 12 Nov 2009 08:26:24 +0100
On 12.11.2009 04:51, Noons wrote:
> On Nov 12, 11:26 am, joel garry <joel-ga..._at_home.com> wrote:
>>> problems with it. It'll go away, I'm sure. But did it really need to >>> be like this? >> I'm leaning towards "yes, meatlink was so creaky and fungusoid, it >> did." And yes, I'm one of the loudest squawkers about it. But this >> too will pass, just like the Sidekick fiasco, and Audi sudden >> acceleration, and hacking of Apple keyboards. Oh wait, that last one >> just started.
> We disagree here. I didn't have the slightest problem with old
> It did its job quite well, metaphorical adjectives apart.
> Of course: it didn't support OCM. But hey: I never asked for OCM
> neither did a lot of users. It's an imposition from Oracle: not
> not asked for. To cause this mayhem and bad blood with clients for
> single reason of updating something that works so that something else
> one asked for could be supported, is sheer madness.
Sorry for the rant.
-- remember.guy do |as, often| as.you_can - without end http://blog.rubybestpractices.com/Received on Thu Nov 12 2009 - 01:26:24 CST