Few points i'd like to weigh in on :)

  • Its software, not a religion. I personally don't care what Microsoft do or how they do it, its business and in truth their is no room for product loyalty in terms of clients. If XAML prooves to be the next wave in terms of innovative "No touch Deployment" strategy, all the better for the world, as lets face it, the "Browser-ware" has been ear marked for upgrade - as to be blunt, its crap and needs a major overhaul. Products like FLEX allow one to flirt with the notion of having a thickware client delivered over the web, and not just in a browser either - better yet, its here, now and available and its platform is well seeded. I'm actually going to enjoy the two worlds, Microsoft and Adobe and to simply place Microsoft on this mantle of "Evil" is umm, well sorry, ignorant. Let the concepts they have on the table swirl around a while before you make rash decisions and choices over which is the better of the two as - i see them both working in a cohesive manner?

  • AJAX is a freakin one trick poney, and all are correct in saying that its got a dirty little secret. When people ask me to benchmark the two, i always say this "Remove XmlHttpRequest, Remove XML, come back to these parts late, now build your UI?" - this is were the blind disciples suddenly have an awareness of "oh gee, yeah, the UI, umm..Bindows.NET? or the prev mention product". I've done copious amount of apps in DHTML and it was my "thing" back in the day, that is until [EMAIL PROTECTED] showed me a nifty little product called Royale back in the day - i immediately retired my DOM boots and went flash 100% as it was and still is the better choice. Nothing gets my propella head going better then seeing an app i wrote work on all platforms equally and with no fuss? thats gotta be worth the price no?

  • Google are already mucking around with SWF compatability and Google is one of these darling products where if there's a majority say in how content is stored, they'll find a way to mine it. Its what they do, index copious amounts of data to allow us the folk online to access and scrap. You can easily setup deep linking in FLEX along with submiting pre-built sitemaps to Google so the whole weight about "indexing won't work with my swf" is umm, bluntly, load of crap. Its more, about adjusting development mode(s). That being said, who the hell wants an Application indexed in google anyway? FLEX is for Rich Internet Applications, the fact you want to use it for a "cool website" to me just doesn't hold water and if you do, well... its XML? write an XLST style translation to seperate the content from swf (using DHTML you can overlay an iframe or some slight of hand trickery to get well seeded and what not). Seperate your content from the swf, i mean "think" about how FLEX works and stop treating it like a web-centric situation.

  • Browsers are here to stay? or are they being used less? - lets face it when you have situations like XBOX 360 hitting the shelves and various other non-pc specific platforms suddenly becoming "Internet" aware, where does one see the browser market sitting? Do you think Macromedia folks are attacking the mobile space because its fun? Anyone can see that if Macromedia were to dominate the mobile space in terms of delivery channel(s) and does so that its easy to develop to? who wouldn't want it in their next-gen hardware?

    Personally, my believe is that IE7 was graciously giving an upgrade / update soley for the purpose of getting the online folk hooked on this darn tootin cool concept called WebFX. Once that gets some traction, then we can revisit the "browser is dead" argument.(imagine a world where you could load an XAML based application and then tab go to a seperate website and load a FLEX application, or better yet, one XAML app with FLEX swf inside it???)

  • Office 12 is to be feared alongside openoffice, as you have to sort of take a step back in many ways and see how they will play a roll in our "future", saving as XML? woah, major leap forward in thinking is not?

If you take a sobering step back and think more on why XAML or MXML was "conjured" up from various inspirations and what not, its easy from my perspective to settle on one thought - it was made to make our lives the developers easier. Products like FLEX, AJAX, UAX, XUL, AXML etc etc will all be ranted and raved about but it soley comes down to internal politics within a company and which brochure a manager read on a flight (heh i've heard that a lot of

I recently heard that PS3 had the better performance overall then XBOX 360 (personally couldn't care), yet that argument was followed up by the fact that sure XBOX 360 may have 10 fps slower then PS3, but Microsoft made it a concious effort to provide SDK for the bloody thing (counter-act moding) and did their upmost best to make it easier for developers to write stuff for it. Point? Developers..Developers..Developers..Developers..Developers..Developers..Developers.. as Balmer would put it... and as Macromedia puts it "Experience Matters"... Devlopers need to make stuff faster then they did 20 years ago, and worse, in much more of a rapid amount of time while still giving the end solution a point of difference in terms of either interaction or business. Thus, combining the two elements and you have to so far align with FLEX, it delivers a much richer UI and in a much faster effort ratio (provided you learn the language).

Rants... rock no?

Anyway FLEX = XML, keep that always in the front of your mind.

--
Regards,
Scott Barnes
http://www.mossyblog.com

--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com




SPONSORED LINKS
Web site design development Computer software development Software design and development
Macromedia flex Software development best practice


YAHOO! GROUPS LINKS




Reply via email to