This is funny, it took me less then 2 weeks to rewrite the cross
compiler for alternate output formats and we are talking about not
competeing.
A team is only as strong as it's weakest link. That link is not going
to be me. I have a feeling Daniel this will get ironed out. Once Erik,
Alex and Frank get this figured out, there will be something next to
figure out, big deal.
because I can't see flex to compete in near future.
By all means man keep working on your project. See a scientist always
invents meaningful things on their own time, the masses always follow
an "intact" idea. I see the chances of Flex eventually competing in
the HTML5/JS sector as above 50%, thus my involvement in this project.
Don't take life to seriously, it will eat you apart.
Mike
Quoting Frank Wienberg <fr...@jangaroo.net>:
On Sat, Dec 22, 2012 at 12:19 AM, Daniel Wasilewski
<devudes...@gmail.com>wrote:
With all respect, all the talks on this subject just convinced me more to
continue my work on BixBite project, because I can't see flex to compete in
near future.
Dan, what exactly in this discussion made you think that we don't care
about performance?
I am with Alex that there is enough time for moaning and complaining about
alleged performance problems when we have a real-world application
cross-compiled.
At the same time, I am convinced that if there is a performance bottleneck,
it will be in the rendering (canvas, DOM), not in the actual application
code. For example, our complex browser UI application only spends about 10%
CPU time in JavaScript code. All the rest is the browser computing styles,
DOM repaint / reflow, and the actual rendering.
My experiments with running cross-compiled Flash games on iOS had their
best performance boost with every iOS update, providing increased canvas
rendering speed and JavaScript performance.
-Frank-
--
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com
