Hi All,
someone said adobe will not support flex in 5 to 10 years time and hence it
poses a threat to flex developers.
I beg to deffer because we need to clearly distinct a vendor from her products.
A vendor changes focus to another phase of technology
does not mean the vendor will outrightly discard her old and stable
products.Its discouraging though that flex will not practically evolve to a
better
framework if adobe denies support in the nearest future but the consolation is
the relative strength,robustness and stability of the framework when compared
with other RIAs
If technologies like cobol, powerbuilder,Vb6, classic ASP (though not RIAs) are
still existing in the industry even though they are no longer in vogue
i dont see a framework that is rich, stable ,platform independent and shows
cross browser compatibility face out in the market at all.
Look, i cant imagine a standard browser (in existence or still to come) that
will deny compatibility with flash and yet expect to be widely used?
No browser vendor will shoot herself on the leg by taking such a weak strategy.
If you see a possible end for flex, what would you say of silverlight? (lol)
Yet silverlight users are optimistic that Microsoft will find
a way to integrate the framework to all other browsers
The advent of RIAs addresses a critical need that is so significant, it saves
you from the hassles of html/JS/CSS in the areas of presentation consistency
across browsers and business security (though .swf files can be decompiled but
its not a piece of cake) and i strongly believe flex is the most powerful RIA
in the market, i cant even compare zkoss with it.
Such frameworks are not abandoned, they come to stay !!!
Warm Regards
Tunde Majolagbe
+2348028320370, 018782170.
*Exchange a Dollar, we still have ONE each, exchange an idea, we have TWO each.
*Calm Down!!! It’s just a mirage, like other worries it will soon fade away.
From: Alex Harui
To: "flexcoders@yahoogroups.com"
Sent: Thursday, 12 January 2012, 16:19
Subject: Re: [flexcoders] Re: Flex alternatives
I’ve never used COBOL, but I haven’t heard anyone say they really liked working
in with it. That’s not true for Flex so even if it gets marginalized because
it always remains locked to ActionScript and FlashPlayer, it may not be the
subject of cursing.
I’m not in disagreement that in the long term, the advantages of
Flex/ActionScript/FlashPlayer will be diminished by advances in the HTML/CSS/JS
stack. That’s why Adobe has made a major strategic shift to become the tooling
leader in the HTML stack. But that doesn’t mean that you should stop using
Flex/ActionScript/FlashPlayer right now.
Many folks who work with HTML/CSS/JS, even using the many libraries and
development methodologies available for it, still feel like the Flex paradigm
is superior. Apparently, even Google agrees because they are trying to create
their own version of that paradigm with DART. While translated code is never
as good, the productivity advantages of a better paradigm have been pretty much
proven to be worth it, otherwise, Flex wouldn’t have been that successful
either since MXML isn’t as efficient as pure ActionScript, and Google wouldn’t
have invested so much in writing their website logic in Java and/or Google
Closure and/or DART.
There is general support in the Apache Flex project for exploring ways of using
the Flex paradigm to create HTML5 apps. Those working on the project are
motivated to future-proof their investment in Flex. I don’t see any technical
issue blocking us from translating the paradigm to HTML5, and I invite all
those who like the Flex paradigm to participate. But at the same time, there
is lots of work to be done, lots of solutions to be built, and lots of money to
be made on the Flex/AS/FP stack while we wait for the HTML5 stack to deliver on
its promises.
On 1/12/12 3:37 PM, "Ron G" wrote:
>
>
>
>
>I think you make my point for me by comparing the future of Flex to COBOL.
>Yes, it's still around, but we all wish it wasn't and curse it everytime we
>have to deal with it. As you say, "it is hard to get out." So, yes, I still
>have projects written in Flex that will undoubtedly continue to run for years
>to come. But, it's hardly a justification for continuing to develop in
>COBOL...er, uh, I mean Flex.
>
>As you say, "the need for Flash in the browser will likely diminish". Again,
>you help make my point against using Flex or FlashBuilder. I find it amusing
>that some have suggested that Flex and FlashBuilder could be retooled to
>render HTML5 pages. It confounds me as to why I would want to write MXML and
>AS3 so it can be translated to HTML and JS. If that is the desired end
>product, then I suggest developers just develop in HTML and JS to begin wit