<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Why wait for Avalon?</title><link>http://blogs.msdn.com/dmassy/archive/2004/04/26/120390.aspx</link><description>Frank Hillman responded to my previous post of Is XAML a big deal? and asks Why wait for avalon? especially when there are some great tools and libraries available today. That's a great question. In short I don't think you should wait. If you need to</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Why wait for Avalon?</title><link>http://blogs.msdn.com/dmassy/archive/2004/04/26/120390.aspx#120893</link><pubDate>Tue, 27 Apr 2004 08:12:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:120893</guid><dc:creator>Dan Becker</dc:creator><description>Hi Dave -- I'm excited about Avalon because it looks like I'll be able to use some truly high-res (200dpi+) displays without having Windows GUI meltdowns, as happens today when running XP with &amp;quot;Large Fonts&amp;quot;. I've been playing with some 'higher' resolution displays and I just LOVE the increased sharpness &amp;amp; text readability. I feel it makes a HUGE difference in lowering a barrier between me and the information inside my computer. Take care of just that, and Avalon will justify a Longhorn upgrade. All the rest is frosting for me. &lt;br&gt;&lt;br&gt;Did I mention I like frosting? </description></item><item><title>re: Why wait for Avalon?</title><link>http://blogs.msdn.com/dmassy/archive/2004/04/26/120390.aspx#121197</link><pubDate>Tue, 27 Apr 2004 17:21:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:121197</guid><dc:creator>Aaron Lewis</dc:creator><description>I'm eager to have Avalon running on my boxes at home, but mostly because I want to be a user of the goodies it'll bring.  Most of our internal tools will probably be rewritten (or modified) where appropriate to take advantage of the enhancements when it makes sense, but...&lt;br&gt;&lt;br&gt;Though, as a business writing web-based software for consumption by the general public running whatever operating system they please (and whatever version), there probably won't be a publicly released app written for Avalon from my company any time in the forseeable future.  We'll have some killer-looking internal apps that 2 people will love, though!</description></item><item><title>Developers Everywhere Agree</title><link>http://blogs.msdn.com/dmassy/archive/2004/04/26/120390.aspx#160884</link><pubDate>Mon, 21 Jun 2004 01:13:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:160884</guid><dc:creator>Joe Aggregate Developer</dc:creator><description>I'd like a product strong enough to stand on it's own merrits, at the time of realease. One that doesn't hide behind buzzwords, or marketing pep-rallies as a substitute for technical excellence.&lt;br&gt;&lt;br&gt;Surly, developers of all people are both ready and prepared for a future that they'll know when they see. That is, one that doesn't require several quarters of &amp;quot;psyching up&amp;quot; for.</description></item></channel></rss>