Centaurs Identity
Not so random thoughts from my own personal individual point of view
DEEP BLUE is not about the famous IT company
Watched "DEEP BLUE".  It was really a great movie.  I just can't believe if the movie can ever be possible to see, because many of the scenes I just can't be sure how human beings could shoot.  Two hours of healing experience.  If you decide to wait for a DVD, please don't forget to have large screens plus a good set of speakers.
First time in a limo
Yesterday was my wife's birthday and we went out to our favorite Sushi restaurant at Roppongi.  Food was definitely great, no question about it.  And we asked the limo service to come back to our home.  It certainly made us feel we are some important persons.  Below is a picture taken using cell phone camera, inside the Lincoln 72 Inches Stretch Limousine.
 
Spasky to Bush: Arrest me!
Spasky to Bush: Arrest me!
 
Mr. Habu, Japan's Shogi champion also sent an email to the Japanese Prime Minister Koizumi to ask his release.  I was surprised Bobby Fischer has been in Japan for quite a long time, but it has not been that secret among pro- and amateur chess players in Japan.
Visiting Seattle
Seattle Weather
 
Woo...  Showers, showers and showers.
Hope I can have some fun in this longer weekend (my Sunday is your Saturday!).
To WinForms 2.0, or to Avalon, that will be the question
The question then becomes, do I commit to Windows Forms, only to throw much of it out as I move to Avalon? 
 
The answer is Yes.  [A blog to the tune of James]
 
I believe, that move to CLR/Fx is no question.  The problem is to move to "2.0" after RTM or stay "1.1" even for the year 2005.
 
Vector based graphics will be huge for GUI developers.  But Longhorn/Avalon-powered XP will not be users' choice for several years, making one could focus on WinForms for now.  Whidbey WinForms is huge too, but I don't know if we should really deploy Whidbey based WinForms and related technologies such as ClickOnce.  If it will be a pain for customers to install .NET Fx, we may want to postpone until Avalon/XP will be available.  There will be enough days to work behind the scenes to prepare installation.
Another CTP is coming...
I’m excited to say that today we signed off on the the last few issues and started the release process for the next Community Technology Preview.  You should be able to get the bits off of MSDN later this week.  [Rick LaPlante's WebLog]
 
So, it will be announced at TechEd Yokohama next week.
 
Because ".NET Fx 2.0" may not be a significant release in terms of CLR and BCLs, the Team System feature is the one which we should carefully look at.
 
Update(2004-09-01JST): It's up for MSDN Subscription.
And now Longhorn...
Microsoft Announces 2006 Target Date for Broad Availability Of Windows "Longhorn" Client Operating System
 
Microsoft announced:
  • Longhorn Client will be out in 2006
  • WinFS will be beta when Longhorn Client is out
  • Avalon and Indigo will be on XP and 2K3 and will be out in 2006
 
Now, .NET Fx 2.0 (a.k.a. Whidbey) will ship in later 2005 ("later" is my wild guess).  A year later from the event, .NET Fx 3.0 (a.k.a. WinFX) will ship.  I don't know why I have to put my hands dirty with Whidbey.  Given the fact that 1.0 and 1.1 Fx need a few years to be the choice for development team, it seems fair to assume that Whidbey will need at least another year to spread.  And when people already knows that they will have THE innovation a year later, who will use Whidbey?  Two more years with Everett (1.1 Fx) sounds absolutely fine for me.
Whidbey is reverting back
First I found this days ago from ASP.NET team, and then this from System.Xml team.  Looks like Whidbey is reverting back to be Everett...?
 
The status of mobile ASP.NET controls does not bother me at least for now, but System.Xml is definitely one of my favorite(?) namespaces, and I should always consider its climate.
 
I for one don't love DOM programming model at all and I firmly believe that XML programmer does not have to learn DOM anymore.  Many programming environments offer various sort of features that keep programmers away from DOM model.  System.Xml seems no different here, but we will see.
 
For now, we have to wait for Beta 2 to see what "reverting the XPathDocument to what it was in v1.1" really means, as well as XmlDocument's perf improvements, and the results of editable XPathNavigator.
Whidbey XPath features need namespace awareness
XmlDataSource.XPath and XPathBinder should be very interesting features, but they don't accept namespace qualified documents.  What a pity.
Time flies...
They are deprecating the SoapFormatter.  I don't think I have to have it anymore, so my vote is "Go ahead and deprecate it".
 
Those were the days, when SoapFormatter showed us how we can interop using objects serialized in XML.  SoapFormatter was said to be one of the most conformant implementation of SOAP Section 5.  Those were the days that "real geeks use Remoting, ASMX is for kids".  Now in 2004, we are in the world where doc/lit is the only path to survive, we don't believe Remoting provides interop anymore.
 
Amazon recognized the move too, and the latest update has doc/lit endpoint instead of rpc/encoded.