by Michael S. Kaplan, published on 2007/02/22 06:01 -05:00, original URI: http://blogs.msdn.com/b/michkap/archive/2007/02/22/1738268.aspx
(The Kramer vs. Kramer allusion doesn't work here really, something about the scansion I think?)
You may recall when in two recent posts I wrote about two things that suck about CurrentUICulture.
Well, it turns out that the MapPoint Web Services SDK has managed to get half of the problem solved in their own version of the CultureInfo class contained in the MapPoint Web Service Class Library.
Their re-factored version has just two properties (Lcid and Name) certainly takes care of my concerns about the weight oft he object that I rambled on about in that first post.
Of course they managed to not only keep the screwed up name but add to the confusion by making its name identical to the other, different object while changing the case of 50% of the properties it supports.
And of course the docs with statements like "The default culture is English—United States." won't make a lifelong fan of me.... and neither will their puny list of Supported Languages.
I admit I was initially excited about an attempt to solve some of the problem, but I am not going to be shallow enough to find anyone or anything "classy" just because they shed a few pounds -- other flaws cannot be ignored....
This post brought to you by œ (U+0153, a.k.a. LATIN SMALL LIGATURE OE)