<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:pingback="http://madskills.com/public/xml/rss/module/pingback/" version="2.0">
  <channel>
    <title>Richard Campbell Blogs Too - Longhorn</title>
    <link>http://www.campbellassociates.ca/blog/</link>
    <description>Surrendering to the Inevitable</description>
    <language>en-us</language>
    <copyright>Richard Campbell</copyright>
    <lastBuildDate>Wed, 16 May 2007 13:02:15 GMT</lastBuildDate>
    <generator>newtelligence dasBlog 1.9.7067.0</generator>
    <managingEditor>richard@campbellassociates.ca</managingEditor>
    <webMaster>richard@campbellassociates.ca</webMaster>
    <item>
      <trackback:ping>http://www.campbellassociates.ca/blog/Trackback.aspx?guid=d799297e-1074-4aab-a2ef-8ede2b1bcdbe</trackback:ping>
      <pingback:server>http://www.campbellassociates.ca/blog/pingback.aspx</pingback:server>
      <pingback:target>http://www.campbellassociates.ca/blog/PermaLink,guid,d799297e-1074-4aab-a2ef-8ede2b1bcdbe.aspx</pingback:target>
      <dc:creator>
      </dc:creator>
      <wfw:comment>http://www.campbellassociates.ca/blog/CommentView,guid,d799297e-1074-4aab-a2ef-8ede2b1bcdbe.aspx</wfw:comment>
      <wfw:commentRss>http://www.campbellassociates.ca/blog/SyndicationService.asmx/GetEntryCommentsRss?guid=d799297e-1074-4aab-a2ef-8ede2b1bcdbe</wfw:commentRss>
      <body xmlns="http://www.w3.org/1999/xhtml">
        <p>
Greg and I dive into a discussion on 64 bit technologies on the desktop and server
in the <a href="http://www.runasradio.com/default.aspx?showNum=6">6th show of RunAs
Radio with Wes Miller</a>. 
</p>
        <p>
As always, you can send email to <a href="mailto:info@runasradio.com">info@runasradio.com</a> or
comment here for feedback on shows you'd like to see, questions, criticisms, etc.
</p>
        <p>
 
</p>
        <img width="0" height="0" src="http://www.campbellassociates.ca/blog/aggbug.ashx?id=d799297e-1074-4aab-a2ef-8ede2b1bcdbe" />
      </body>
      <title>RunAs Radio #6: Wes Miller on 64 bit </title>
      <guid isPermaLink="false">http://www.campbellassociates.ca/blog/PermaLink,guid,d799297e-1074-4aab-a2ef-8ede2b1bcdbe.aspx</guid>
      <link>http://www.campbellassociates.ca/blog/PermaLink,guid,d799297e-1074-4aab-a2ef-8ede2b1bcdbe.aspx</link>
      <pubDate>Wed, 16 May 2007 13:02:15 GMT</pubDate>
      <description>&lt;p&gt;
Greg and I dive into a discussion on 64 bit technologies on the desktop and server
in the &lt;a href="http://www.runasradio.com/default.aspx?showNum=6"&gt;6th show of RunAs
Radio with Wes Miller&lt;/a&gt;. 
&lt;/p&gt;
&lt;p&gt;
As always, you can send email to &lt;a href="mailto:info@runasradio.com"&gt;info@runasradio.com&lt;/a&gt; or
comment here for feedback on shows you'd like to see, questions, criticisms, etc.
&lt;/p&gt;
&lt;p&gt;
&amp;nbsp;
&lt;/p&gt;
&lt;img width="0" height="0" src="http://www.campbellassociates.ca/blog/aggbug.ashx?id=d799297e-1074-4aab-a2ef-8ede2b1bcdbe" /&gt;</description>
      <comments>http://www.campbellassociates.ca/blog/CommentView,guid,d799297e-1074-4aab-a2ef-8ede2b1bcdbe.aspx</comments>
      <category>Longhorn</category>
      <category>PodCasting</category>
      <category>RunAs Radio</category>
    </item>
    <item>
      <trackback:ping>http://www.campbellassociates.ca/blog/Trackback.aspx?guid=1939148c-c259-470a-ad5b-661783fc86a6</trackback:ping>
      <pingback:server>http://www.campbellassociates.ca/blog/pingback.aspx</pingback:server>
      <pingback:target>http://www.campbellassociates.ca/blog/PermaLink,guid,1939148c-c259-470a-ad5b-661783fc86a6.aspx</pingback:target>
      <dc:creator>
      </dc:creator>
      <wfw:comment>http://www.campbellassociates.ca/blog/CommentView,guid,1939148c-c259-470a-ad5b-661783fc86a6.aspx</wfw:comment>
      <wfw:commentRss>http://www.campbellassociates.ca/blog/SyndicationService.asmx/GetEntryCommentsRss?guid=1939148c-c259-470a-ad5b-661783fc86a6</wfw:commentRss>
      <slash:comments>1</slash:comments>
      <body xmlns="http://www.w3.org/1999/xhtml">
        <p>
I'm not a huge Wiki fan, but Microsoft putting software into the Open Source domain
is pretty cool.
</p>
        <p>
If you've never heard of Wikis, you're not alone, they're kind of a weird concept
(and product), a web site that's fully editable by virtually anyone, so that you get
this sort of disorganized amorphous blob of potentially useful information that keeps
moving and changing... wow, its just like the Internet!
</p>
        <p>
Anyway, Wikis were invented by <a href="http://c2.com/cgi/wiki?WardCunningham">Ward
Cunningham</a>, a terribly clever fellow who now works at Microsoft (which is, after
all, the land of terribly clever people). <a href="http://www.flexwiki.com/">FlexWiki</a> was
developed by <a href="http://blogs.msdn.com/dornstein/">David Ornstein</a>, a Program
Manager for Longhorn. Do these two facts have any relation? I dunno.
</p>
        <p>
This is the third time Microsoft has posted software to SourceForge, the first, back
in March of 2004 was the <a href="http://sourceforge.net/projects/wix">Windows Install
XML (WiX) toolset</a>. Second is the <a href="http://sourceforge.net/projects/wtl">Windows
Template Library</a>, released in May. Both these projects are libraries, and so not
of any interest to regular mortals, however, they are some of the most popular projects
on SourceForge, with 103,000 and 22,000 downloads respectively - the page view counts
are huge!
</p>
        <p>
FlexWiki, as with WiX and WTL are released under the <a href="http://www.opensource.org/licenses/cpl.php">Common
Public Licence</a> and part of <a href="http://www.microsoft.com/resources/sharedsource/default.mspx">Microsoft's
Shared Source Initiative</a>. 
</p>
        <p>
FlexWiki represents the closest thing to a product released into the wilds of Open
Source by Microsoft. It'll be interesting to see what comes next.
</p>
        <img width="0" height="0" src="http://www.campbellassociates.ca/blog/aggbug.ashx?id=1939148c-c259-470a-ad5b-661783fc86a6" />
      </body>
      <title>FlexWiki Released to SourceForge...</title>
      <guid isPermaLink="false">http://www.campbellassociates.ca/blog/PermaLink,guid,1939148c-c259-470a-ad5b-661783fc86a6.aspx</guid>
      <link>http://www.campbellassociates.ca/blog/PermaLink,guid,1939148c-c259-470a-ad5b-661783fc86a6.aspx</link>
      <pubDate>Wed, 29 Sep 2004 00:08:46 GMT</pubDate>
      <description>&lt;p&gt;
I'm not a huge Wiki fan, but Microsoft putting software into the Open Source domain
is pretty cool.
&lt;/p&gt;
&lt;p&gt;
If you've never heard of Wikis, you're not alone, they're kind of a weird concept
(and product), a web site that's fully editable by virtually anyone, so that you get
this sort of disorganized amorphous blob of potentially useful information that keeps
moving and changing... wow, its just like the Internet!
&lt;/p&gt;
&lt;p&gt;
Anyway, Wikis were invented by &lt;a href="http://c2.com/cgi/wiki?WardCunningham"&gt;Ward
Cunningham&lt;/a&gt;, a terribly clever fellow who now works at Microsoft (which is, after
all, the land of terribly clever people). &lt;a href="http://www.flexwiki.com/"&gt;FlexWiki&lt;/a&gt; was
developed by &lt;a href="http://blogs.msdn.com/dornstein/"&gt;David Ornstein&lt;/a&gt;, a Program
Manager for Longhorn. Do these two facts have any relation? I dunno.
&lt;/p&gt;
&lt;p&gt;
This is the third time Microsoft has posted software to SourceForge, the first, back
in March of 2004 was the &lt;a href="http://sourceforge.net/projects/wix"&gt;Windows Install
XML (WiX) toolset&lt;/a&gt;. Second is the &lt;a href="http://sourceforge.net/projects/wtl"&gt;Windows
Template Library&lt;/a&gt;, released in May. Both these projects are libraries, and so not
of any interest to regular mortals, however, they are some of the most popular projects
on SourceForge, with 103,000 and 22,000 downloads respectively - the page view counts
are huge!
&lt;/p&gt;
&lt;p&gt;
FlexWiki, as with WiX and WTL are released under the &lt;a href="http://www.opensource.org/licenses/cpl.php"&gt;Common
Public Licence&lt;/a&gt; and part of &lt;a href="http://www.microsoft.com/resources/sharedsource/default.mspx"&gt;Microsoft's
Shared Source Initiative&lt;/a&gt;. 
&lt;/p&gt;
&lt;p&gt;
FlexWiki represents the closest thing to a product released into the wilds of Open
Source by Microsoft. It'll be interesting to see what comes next.
&lt;/p&gt;
&lt;img width="0" height="0" src="http://www.campbellassociates.ca/blog/aggbug.ashx?id=1939148c-c259-470a-ad5b-661783fc86a6" /&gt;</description>
      <comments>http://www.campbellassociates.ca/blog/CommentView,guid,1939148c-c259-470a-ad5b-661783fc86a6.aspx</comments>
      <category>Development</category>
      <category>Longhorn</category>
      <category>Open Source</category>
    </item>
    <item>
      <trackback:ping>http://www.campbellassociates.ca/blog/Trackback.aspx?guid=7fff9613-ab6e-4a80-926d-f912ad5507c7</trackback:ping>
      <pingback:server>http://www.campbellassociates.ca/blog/pingback.aspx</pingback:server>
      <pingback:target>http://www.campbellassociates.ca/blog/PermaLink,guid,7fff9613-ab6e-4a80-926d-f912ad5507c7.aspx</pingback:target>
      <dc:creator />
      <wfw:comment>http://www.campbellassociates.ca/blog/CommentView,guid,7fff9613-ab6e-4a80-926d-f912ad5507c7.aspx</wfw:comment>
      <wfw:commentRss>http://www.campbellassociates.ca/blog/SyndicationService.asmx/GetEntryCommentsRss?guid=7fff9613-ab6e-4a80-926d-f912ad5507c7</wfw:commentRss>
      <slash:comments>1</slash:comments>
      <body xmlns="http://www.w3.org/1999/xhtml">
        <p>
Man, I'm a huge fan of Jim Allchin. He's straight talking, serious and kicks ass.
My current favorite quote from Jim: “Malware. I want it dead.” And follows
that by saying that he hadn't been able to deliver that 100% for XP SP2. But they're
still plugging away.
</p>
        <p>
But the topic of the day was Longhorn. Most people know that the name comes from the
Longhorn bar that sits between Whistler (the code name of Windows XP) and Blackcomb
(which was supposed to be the next version of Windows). But the reality of Longhorn
is that it has grown to be an amazing and complex version of Windows. The highlight
peices have been <a href="http://msdn.microsoft.com/Longhorn/understanding/pillars/avalon/default.aspx">Avalon</a>, <a href="http://msdn.microsoft.com/Longhorn/understanding/pillars/Indigo/default.aspx">Indigo</a> and <a href="http://msdn.microsoft.com/Longhorn/understanding/pillars/WinFS/default.aspx">WinFS</a>.
Microsoft has promised a stunning amount of new functionality in Longhorn, and Jim
is promising to deliver on it, <a href="http://www.microsoft.com/presspass/press/2004/Aug04/08-27Target2006PR.asp">just
in a different form</a>.
</p>
        <p>
What's happened is that the Windows team is fixing the date of Longhorn - for “holiday
time 2006.” To do that, they are breaking up the delivery of all these different
features.
</p>
        <p>
The exciting part is that versions of Avalon and Indigo are going to be made available
for Windows XP and Windows Server 2003. This is great news for developers, we're going
to get a chance to build software utilizing the capabilities of these subsystems without
having to have Longhorn. We don't have to drive our customers to the latest OS to
take advantage of this new technology.
</p>
        <p>
WinFS is being pushed back, to be delivered after Longhorn. The way Jim talked about
it, it sounds to me like WinFS is growing in scope - the more they realize the power
of object based data storage, the more development they need to do. Jim said they
realized they don't want to ship the WinFS client component without the server component,
and that means they need more time. It makes sense to me, it sounds like its going
to be worth the wait. And it doesn't sound like its going to be long after, either.
Jim says that WinFS will be in beta when Longhorn ships. That pretty much means that
WinFS must ship in 2007 - Microsoft rarely ever goes over a year in beta.
</p>
        <p>
The obvious question is “what's left for Longhorn?” and the answer is
plenty. Sure, Avalon, Indigo and WinFS have been the highlight elements, but there
is plenty more in the plan. A vastly more advanced search system is key, along with
better functionality all around. The new display driver model of Longhorn is going
to make a huge difference, I don't think we'll see the full power of Avalon until
that is in place. A vastly improved deployment engine is going to make a big difference
to anyone handling more computers than they can reach easily in one room.
</p>
        <p>
In the end, the room applauded Jim, not just for being forthright about the realities,
but because I think everyone here realized that this new plan is a better plan. Waiting
for a massive shipment of all new code is not the best way to go - break the important
bits down and get them out the door. That way we can kick the tires, explore the capabilities,
and feed back into Microsoft to make them better. When the whole comes together, it'll
be vastly superior to what we originally came up with at the beginning.
</p>
        <p>
 
</p>
        <img width="0" height="0" src="http://www.campbellassociates.ca/blog/aggbug.ashx?id=7fff9613-ab6e-4a80-926d-f912ad5507c7" />
      </body>
      <title>Allchin lays down on Longhorn</title>
      <guid isPermaLink="false">http://www.campbellassociates.ca/blog/PermaLink,guid,7fff9613-ab6e-4a80-926d-f912ad5507c7.aspx</guid>
      <link>http://www.campbellassociates.ca/blog/PermaLink,guid,7fff9613-ab6e-4a80-926d-f912ad5507c7.aspx</link>
      <pubDate>Fri, 27 Aug 2004 20:46:42 GMT</pubDate>
      <description>&lt;p&gt;
Man, I'm a huge fan of Jim Allchin. He's straight talking, serious and kicks ass.
My current favorite quote from Jim: &amp;#8220;Malware. I want it dead.&amp;#8221; And follows
that by saying that he hadn't been able to deliver that 100% for XP SP2. But they're
still plugging away.
&lt;/p&gt;
&lt;p&gt;
But the topic of the day was Longhorn. Most people know that the name comes from the
Longhorn bar that sits between Whistler (the code name of Windows XP) and Blackcomb
(which was supposed to be the next version of Windows). But the reality of Longhorn
is that it has grown to be an amazing and complex version of Windows. The highlight
peices have been &lt;a href="http://msdn.microsoft.com/Longhorn/understanding/pillars/avalon/default.aspx"&gt;Avalon&lt;/a&gt;, &lt;a href="http://msdn.microsoft.com/Longhorn/understanding/pillars/Indigo/default.aspx"&gt;Indigo&lt;/a&gt; and &lt;a href="http://msdn.microsoft.com/Longhorn/understanding/pillars/WinFS/default.aspx"&gt;WinFS&lt;/a&gt;.
Microsoft has promised a stunning amount of new functionality in Longhorn, and Jim
is promising to deliver on it, &lt;a href="http://www.microsoft.com/presspass/press/2004/Aug04/08-27Target2006PR.asp"&gt;just
in a different form&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
What's happened is that the Windows team is fixing the date of Longhorn - for &amp;#8220;holiday
time 2006.&amp;#8221; To do that, they are breaking up the delivery of all these different
features.
&lt;/p&gt;
&lt;p&gt;
The exciting part is that versions of Avalon and Indigo are going to be made available
for Windows XP and Windows Server 2003. This is great news for developers, we're going
to get a chance to build software utilizing the capabilities of these subsystems without
having to have Longhorn. We don't have to drive our customers to the latest OS to
take advantage of this new technology.
&lt;/p&gt;
&lt;p&gt;
WinFS is being pushed back, to be delivered after Longhorn. The way Jim talked about
it, it sounds to me like WinFS is growing in scope - the more they realize the power
of object based data storage, the more development they need to do. Jim said they
realized they don't want to ship the WinFS client component without the server component,
and that means they need more time. It makes sense to me, it sounds like its going
to be worth the wait. And it doesn't sound like its going to be long after, either.
Jim says that WinFS will be in beta when Longhorn ships. That pretty much means that
WinFS must ship in 2007 - Microsoft rarely ever goes over a year in beta.
&lt;/p&gt;
&lt;p&gt;
The obvious question is &amp;#8220;what's left for Longhorn?&amp;#8221; and the answer is
plenty. Sure, Avalon, Indigo and WinFS have been the highlight elements, but there
is plenty more in the plan. A vastly more advanced search system is key, along with
better functionality all around. The new display driver model of Longhorn is going
to make a huge difference, I don't think we'll see the full power of Avalon until
that is in place. A vastly improved deployment engine is going to make a big difference
to anyone handling more computers than they can reach easily in one room.
&lt;/p&gt;
&lt;p&gt;
In the end, the room applauded Jim, not just for being forthright about the realities,
but because I think everyone here realized that this new plan is a better plan. Waiting
for a massive shipment of all new code is not the best way to go - break the important
bits down and get them out the door. That way we can kick the tires, explore the capabilities,
and feed back into Microsoft to make them better. When the whole comes together, it'll
be vastly superior to what we originally came up with at the beginning.
&lt;/p&gt;
&lt;p&gt;
&amp;nbsp;
&lt;/p&gt;
&lt;img width="0" height="0" src="http://www.campbellassociates.ca/blog/aggbug.ashx?id=7fff9613-ab6e-4a80-926d-f912ad5507c7" /&gt;</description>
      <comments>http://www.campbellassociates.ca/blog/CommentView,guid,7fff9613-ab6e-4a80-926d-f912ad5507c7.aspx</comments>
      <category>Development</category>
      <category>Speaking</category>
      <category>Travel</category>
      <category>Longhorn</category>
    </item>
  </channel>
</rss>