<?xml version="1.0" encoding="UTF-8" standalone="yes"?><oembed><version><![CDATA[1.0]]></version><provider_name><![CDATA[Scobleizer]]></provider_name><provider_url><![CDATA[http://scobleizer.blog]]></provider_url><author_name><![CDATA[Robert Scoble]]></author_name><author_url><![CDATA[https://scobleizer.blog/author/scobleizer/]]></author_url><title><![CDATA[Drinking the Adobe&nbsp;coffee]]></title><type><![CDATA[link]]></type><html><![CDATA[<p>The Adobe Engage event is already proving interesting. <a href="http://blog.digitalbackcountry.com/?p=691">Ryan Stewart wins the first report</a> to come through Google Blog Search.</p>
<p>Takeaway? Adobe is indeed coming after developers. It&#8217;s interesting to hear their positioning vs. Microsoft. My post last week pretty much nailed it. Adobe&#8217;s Kevin Lynch says they try to extend the Web where Microsoft looks, he says, to extend Windows.</p>
<p>Adobe&#8217;s weaknesses? Corporate developers are safely in Microsoft&#8217;s camp because Adobe&#8217;s Apollo system (which lets developers build Windows, Mac, or Linux applications) can&#8217;t get to the Windows API (or the Mac API, or Linux&#8217; API).</p>
<p>The other real loser here? Java. Apollo delivers real cross-platform apps that look a lot like what Microsoft always demonstrated with .NET 3.0 (great looking UIs and rich interaction).</p>
<p>But, clearly, Lynch wanted to position Apollo against Microsoft&#8217;s WPF/E, not Java.</p>
<p>Anyway, more later, we&#8217;re sitting through a ton of third-party demos now.</p>
]]></html></oembed>