Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of olegsivokon@gmail.com
 designates 209.85.210.175 as permitted sender)
Received-SPF: pass (google.com: domain of olegsivokon@gmail.com designates
 10.50.161.196 as permitted sender) client-ip=10.50.161.196;
MIME-Version: 1.0
In-Reply-To: 
 <CALorpXeE4Cv7fnCXay+f4x1Lm+Jhzm+N5GkFHEWU3nhYDv2P6A@mail.gmail.com>
References: <4F44A4AE.1030408@leichtgewicht.at>
	<CAJ16SzANnbyM9s9N9YLuUT+z6FiDw=NHeLdw7UWg8p_-djSDAA@mail.gmail.com>
	<B92B97DE-7A9B-4361-B270-6C96D9CB24B1@adobe.com>
	<4F44AFAB.9060002@leichtgewicht.at>
	<33487595652B444690C75E0151928A4B@KORODESKTOP>
	<009001ccf143$2c353890$849fa9b0$@davidarno.org>
	<4F44B516.7000009@leichtgewicht.at>
	<4F44DF0C.7070802@leichtgewicht.at>
	<CANj_=ifKzq=tuH=DfRDLRnvbs=nORF7skt38eTKHd9PS1kyjxQ@mail.gmail.com>
	<CAJQBtg=usjKmq+HE+1ybxjkdq-woVS8pnVBne9gvO8Z4DmL9Wg@mail.gmail.com>
	<CANcBHED02nB-M8_FO6JUDBKtZ4S9HBwJW6-G5oRYfYFZi6RPOA@mail.gmail.com>
	<CAAd0WrY=cpVEjVYDqdQaMSGJaUzEBrjN8bCNEgB7KxA3NASVrA@mail.gmail.com>
	<CALorpXc9i1k-wF2xucEjgtm785UVgNiMvZQdaLQ1EBAyVBt34A@mail.gmail.com>
	<CAJQBtgn680eXH1gK=bHAdMKqOJTn17iVg3CoXyH8dZ-XA7Ojzw@mail.gmail.com>
	<4F4913A7.1030102@dot-com-it.com>
	<CAJQBtg=0gK5Y1PC_Mx+JZm0ae2dLaMekv4-Z2+V-DKe6RHfy8A@mail.gmail.com>
	<CALorpXeE4Cv7fnCXay+f4x1Lm+Jhzm+N5GkFHEWU3nhYDv2P6A@mail.gmail.com>
Date: Sat, 25 Feb 2012 22:17:13 +0200
Message-ID: 
 <CAJQBtgmdBXwWC1kbpZka=QZEN9PZgSEbcn2FLMip_5w2CWOBhg@mail.gmail.com>
Subject: Re: [OT] Flash Platform roadmap
From: Left Right <olegsivokon@gmail.com>
To: flex-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=14dae934051b10c7ac04b9cf902b

--14dae934051b10c7ac04b9cf902b
Content-Type: text/plain; charset=ISO-8859-1

Presentation interface of Flash and Flex interest precisely the prospects,
it's not interesting for a wide range of developers, who write code that
leverages client-server communication, data processing, physics, AI and
many many more. I, for once, being an AS3 programmer at my last job had to
deal purely with only the code that manages some video-peer-to-peer-chat
kind of thing, and the visual side of project never was in my real of
responsibility. However, the must-have visual side of thing (which in my
case was an ideal white screen 600x800 pixels) hindered the process a lot -
Flash player is creepily slow and unproductive when communicating outside.
On tests, you would often want to run 100 copies of the program, but maybe
even more... running so many flash players would be very unhealthy for the
system :)

And, yeah, like Omar Gonzalez says - testing. You may think about testing
as unimportant, but the larger the project is, the higher % of time it
spends in testing. In fact, a project with the development cycle of about a
year may spend 1-2 months in actual development, and the rest is testing.
Not being able to automatically register or send clicks to player is
maddening.

If, as I mentioned it before, the player could have been combined of two
parts, one being the runtime for the code, that expect callbacks from
another part for doing the rendering and piping in the input events - that
would be priceless, as someone (well, someone like me even!) could've
written a mock for the interaction API to send automatically generated
signals back and forth.
This is also where HTML wins on almost all positions - you can automate the
testing, the continuous integration, and make it all run automatically,
saving a lot of work hours for QA personnel...

Best.

Oleg

--14dae934051b10c7ac04b9cf902b--