Linked by Thom Holwerda on Wed 15th Sep 2010 21:49 UTC, submitted by poundsmack
Graphics, User Interfaces "Adobe Flash Player 'Square' is a preview release that enables native 64-bit support on Linux, Mac OS, and Windows operating systems, as well as enhanced support for Microsoft Internet Explorer 9 beta. We have made this preview available so that users can test existing content and new platforms for compatibility and stability."
Permalink for comment 441387
To read all comments associated with this story, please click here.
lemur2
Member since:
2007-02-17

I think it is too early to say that. I have yet to see a javascript game that has the quality and fun level of the best ArmorGames and Kongregate games around. And the reason is obvious : non-Flash technologies are for geeks. If there was an IDE as good as Flash for standard web technologies, maybe the level would improve. But it is not the case.


Are you sure about that?

http://www.earthtimes.org/articles/press/html5-pack-illustrator-cs5...
http://www.cmswire.com/cms/web-content/adobe-lends-weight-to-html-5...
http://www.slashgear.com/adobe-html5-pack-for-dreamweaver-cs5-relea...

And even technology-speaking, HTML5 implementations are far from reaching the already poor performance of Flash, which has the obvious advantage of years of experience with slow computers (though only those running windows).


Where did you get this from?

Maybe Native Client will do the trick, by getting rid of interpreted code altogether. But then I fear that the result will suffer Java-like insanely slow startup performance, while the program's code is being translated to native insert_your_platform_here code. In short, there is still a lot to do before web standards are a serious competitor to Flash. And that's fine, too, as long as somebody else gets Adobe's ass kicked so that they continue to work on making Flash less of a nightmare like they did with 10.1...


Did you realise that most modern javascript engines in browser are actually compilers? I have been told that the jargon for this is "method JIT".

Examples are Google's V8, Apple's nitro, the new Jaegermonkey engine in Firefox, and even the new engine in the IE9 beta, which AFAIK is called Chakra.

http://msdn.microsoft.com/en-us/ie/ff468705.aspx#_ECMAScript5
Introducing “Chakra”, the new JavaScript engine
Script engine performance is just one part of the overall browser performance picture. Script performance in Internet Explorer 8 improved exponentially over that of Internet Explorer 7, and “Chakra”, the new JavaScript engine in Internet Explorer 9 Beta, does it again. The Chakra engine interprets, compiles, and executes code in parallel and takes advantage of multiple CPU cores, when available. For more details, see the IE Team Blog.


As for the "start-up penalty" ... perhaps you haven't considered the implications of provisions such as Firefox's new "App Tabs" feature:

http://blog.mozilla.com/about_mozilla/2010/08/03/firefox-4-app-tabs...
There’s a new feature coming to Firefox 4 that creates a new kind of browser tab known as an “App Tab”. The idea behind App Tabs is that some web sites are more like applications than web pages, such as Google Docs, webmail, Twitter, and web-based feed readers. These are sites that people often keep open all the time, and App Tabs makes that easier and more efficient to do.


For these "App Tabs", the underlying code will only ever have to be downloaded and re-compiled when it changes.

Edited 2010-09-16 23:36 UTC

Reply Parent Score: 2