Home » Adobe, Microsoft

Microsoft D - Another stab at Adobe?

6 February 2008 2 views 4 Comments

And another of the many innovations I have (and have yet to) stumble across is the new declarative (more on that later) language from Microsoft. This is what appears to be a direct aim at combating Adobe’s hopes with AIR, and Flex both in one. The similarities become even more obvious when you see more in depth details on the way the script is coded.

For those who don’t know, Adobe AIR stands for Adobe Integrated Runtime, which is a way for existing designers or developers devigners (thanks Lee) that work in Adobe’s prime field, the internet, to create quick RIAs (AIR backwards, or is it a coincidence) without learning new scripts. The term RIA is as defined by Adobe - Microsoft seems to use this acronym in a fairly different way to Adobe, which I’ll cover more in forthcoming articles.

Flex is (presumably) a branch of the Flash project, fairly old, relying on the mXML code - a implementation of XML (coming back to this too). It publishes Adobe Flash content and it targeted for developers used to XML and AS classes to compile. It can also compile AIR (Flash-based) applications as Flash itself does. The other way (somewhat irrelevant to the article and less-used anyway) is via HTML, but has less favour due to the main reason people compile AIR is little code experience, and easier design.

So, back to MSD. Microsoft’s D is not the actual name, it is a code name given to the project by their team. The code is of a declarative type, which means that instead of instructions on how to compile, it provides a way of declaring what something is like (starting to ring bells, Flex users?).

The similarities get even more painful to watch when you bear in mind how similar MXML and D’s language XAML really is. Microsoft will not reveal the nature of the code but we can easily assume that two types of code, aimed less than normal at developers built on the same framework, that both produce some form of declarative application has a high risk of, perhaps, taking a chunk out of each other’s market share.

Microsoft has inadvertently made it very obvious how they had not seen Adobe AIR coming, and were concerned at it’s release, some would even argue that it’s rapid employment of platform evangelists points at the change in attitude. Not that Adobe haven’t (Lee Brimelow, Serge Jespers) and not that it’s a bad thing - I’m more than glad that Lee will be having more time to devote to his audience.

It’s got a lot to prove, as we have already seen Microsoft linking it’s projects to too many others, squeezing as much as possible out of the revenue from it. Hopefully this will be a simpler project with simple working, because that’s really what a code not targeting developers should do. That’s all we ask!

As a side-note, google around with Windows 7 and you’ll understand what I mean by ‘overhaul’. I’ll write a bit about the changes soon. Just keep an open mind of a non-Bill Gates Microsoft. Big changes are happening (in a roll-neck).

1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)
Loading ... Loading ...

4 Comments »

  • Microsoft D! | guidance.lowicz.pl said:

    [...] Microsoft D - Another stab at Adobe? [...]

  • Microsoft D! | guidance.lubin.pl said:

    [...] Microsoft D - Another stab at Adobe? [...]

  • Dusty said:

    ok, so, a few clarifications, as it seems you don’t have an entire grasp on the concepts:
    First, some definitions of Flex/Air/Silverlight:
    http://www.onflex.org/ted/2008/02/microsoft-vs-adobe-comparable-runtimes.php

    Second, Declarative Programing:
    http://en.wikipedia.org/wiki/Declarative_programming

    MSD takes on Erlang, Haskell and Lisp, it has nothing to do with AIR/Flex. I understand you’re looking at the MXML format and thinking “They’re declaring things, it’s declarative”, but to be quite honest, there’s little or no programming actually done in MXML tags.. the programming happens in blocks, and that falls under the Imperative umbrella. Silverlight already compiles into XAML, which is on the edge of Declarative family of languages, but when you compare XAML/XSL/MXML to actual declarative languages like Erlang and Lisp, it’s easy to see the differences.

  • Lawrence Job (author) said:

    Hahaha - I emailed you back there with my response. In a nutshell your Wiki article contradicts its own definition and we read them differently.

    Further proof that I forgot to mention is this evidence provided by Microsoft- describing XAML

    Consistent presentation model by using XAML, the declarative presentation language used in Windows Vista–based applications.

Leave your response!

Add your comment below, or trackback from your own site. You can also subscribe to these comments via RSS.

Be nice. Keep it clean. Stay on topic. No spam.

You can use these tags:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

This is a Gravatar-enabled weblog. To get your own globally-recognized-avatar, please register at Gravatar.

Related Posts from the Past: