incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From andrei apostolache <apostolache.and...@gmail.com>
Subject Re: Flex -> HTML, Linux and time to say goodbye?
Date Mon, 27 Feb 2012 14:37:41 GMT
I don't understand how these type of discussion is helping Apache Flex.
All the corporations are ignoring Linux development not only Adobe. Flash
Player on Linux wasn't something that Adobe was proud of, and to be honest
all the applications I've been involved weren't targeted or tested on
Linux. And we didn't have any complains/bugs reported in 5 years(because
less than 5% of users were using Linux).
If your main target is Linux users I'm not sure you would be interested on
building apps with Flash/Flex.

Regards,
Andrei.

On Mon, Feb 27, 2012 at 2:22 PM, David Arno <david@davidarno.org> wrote:

> > From: Jeffry Houser [mailto:jeffry@dot-com-it.com]
> > Sent: 27 February 2012 13:37
> >
> > That is inaccurate.  It'll be supported in Chrome; and if other browsers
> implement the new plugin API; those can be supported to.
> Is that true? Have Google said that they will make the plugin available as
> a
> stand-alone download? Everything I've read suggests it will be built into
> the Chrome download and update installers. And what chance other browsers
> supporting the new API? Didn't Firefox help develop it and then drop it?
> The
> available evidence seems to suggest that no other browser will implement
> it.
>
>
> >> For people whose business is
> >> selling Flex apps to Linux users, this is of course very bad news.
> >  Do such people exist?
> They do, but I'm starting to suspect I'm the only such person.
>
> > Because people have no faith in Adobe; and want Flex to outlive a
> dependency on a proprietary runtime.
> OK, let me ask the question another way. If you see HTML5 as the future,
> why
> do you think it a good idea to put your efforts into porting a badly coded,
> difficult to test, framework over to something that can target JavaScript
> (JS), rather than either adopting an existing JS framework, or starting an
> initiative to build a JS-based framework? Maybe it's time we all said
> goodbye to Flex and put our creative skills into developing something more
> future-proof?
>
> David.
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message