incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yiotis Katsambas <>
Subject Re: Flex -> HTML, Linux and time to say goodbye?
Date Tue, 28 Feb 2012 22:10:47 GMT
It's great to see that there are many developers here that use linux. In
one of the linux related announcements there was a mention that only 0.5%
of air-runtime downloads were linux based. As a percentage it sounds
ridiculously low, but this was still over 2 million downloads. When you
take into account the 'demographic' of a linux user, 2 million linux users
refers to a significant portion of the flash community. I assume that the
percentage of linux users within the apache group is a lot higher than the
0.5%.  If linux is important to any more developers out there, it would be
good if you could voice your support. I am sure it helps the runtime team
get a better understanding of how the linux runtime affects the flex
developer community. I work in the visual effects industry and as most
large animation and VFX houses we use linux pretty heavily for some of our
internal applications. Flex gives us a lot of benefits. It offers some
unique functionality for building intuitive interactive graphics-related
application. And since it's flash our apps are cross platform, easy to
deploy, backwards compatible, easy to manage, etc.

I understand that supporting the linux runtime must be very complicated and
costly, and we could help define some acceptable solutions or even some
acceptable limitations. The pepper implementation sounds like an acceptable
solution to us. I also liked the idea that was suggested of having a
headless AIR runtime. We could use that. Besides using it for testing, we
could reuse existing code in command line tools. We could even hack
together a local browser app that connects to a local headless air server
in a way that mimics some of the functionality of a desktop app.

Also... A big thanks to the Adobe folks who obviously put a lot of work on
getting the flash player roadmaps and the white paper out there. This level
of transparency helps us tremendously in planning our development. So


On Tue, Feb 28, 2012 at 5:39 AM, Rafael Santos <
> wrote:

> On Mon, Feb 27, 2012 at 12:26, Left Right <> wrote:
> > Andrei, and that's why I'm developing on Linux for Windows users happily,
> > for many years? :P Why do I need to care what users choose to be their
> > platform - if they want to run their lovely apps on a toaster - that's
> > fine, as long as they are happy, I'll be still using Linux and writing
> for
> > Toaster OS MegaPlus. I will not be happy to work on a toaster instead of
> a
> > PC though. I prefer to test against WinAPI emulation from Linux, then to
> > run actual Windows because of other benefits of Linux. Eventually, I'll
> > test on Windows just the same. But this scheme allows me to cut costs on
> > proprietary OS'es (I don't need to buy them - more importantly, I don't
> > need to buy all sorts of networking solutions from MS, their version
> > control systems and so on - because I just happen to have a better
> > alternative). I would only buy several examples of Windows Home edition
> to
> > test on that - a whole lot cheaper!
> >
> > Best.
> >
> > wvxvw
> >
> > Sorry, I must stop this, because we are already so far from the topic...
> >
> We also develop on Linux, deploy on Linux, but test mainly on Windows and
> MacOS. Our development environment runs far better on Linux than anyother
> OS. But this is also the way we chose to work so every company and
> developer have the right to choose its own. If we stick to Linux we will
> have to live with Chrome without a debugger version of the runtime as well
> (which would be very hard).
> Rafael Santos
> Specta

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