Smokescreen, a JavaScript-Based Flash Player
Tumbleweed writes "How to make Steve Jobs your mortal enemy: Smokescreen, a 175KB, 8,000-line JavaScript-based Flash player written by Chris Smoak at RevShock, a mobile ad startup, and to be open-sourced 'in the near future.' From Simon's blog: 'It runs entirely in the browser, reads in SWF binaries, unzips them (in native JS), extracts images and embedded audio, and turns them into base64 encoded data: URIs, then stitches the vector graphics back together as animated SVG. ... Smokescreen even implements its own ActionScript bytecode interpreter.' Badass!"
Very impressive! However, given Flash's performance issues even when compiled natively for mobile devices, this is more of a proof of concept then something usable.
Better known as 318230.
This sounds better than the actual Flash player! I've been playing with canvas in an effort to get away from Actionscript but this, especially open sourced, sounds like the best of both worlds.
Physics is like sex: sure, it may give some practical results, but that's not why we do it.
I just wonder how efficient it will be for the rendering times. Some flash is already bordering on bloatware. Add in taking it apart and re-rendering and I start to wonder if its worth it to wait that long.
"Computers are a lot like Air Conditioners" "They both work great until you start opening Windows"
Jobs doesn't care about flash content, he cares about flash. If the flash content can be used without flash itself, well, that'd be great.
Not sure why, but slashdot's headline writers are starting to sound more and more like tabloid writers. Why not say "Smokescreen to Adobe: flash off!"
My take is that this proves, perhaps to a significant degree if not completely, that Javascript/HTML5 can do anything that a native Flash engine could do . So why build in Flash? Go straight to Javascript/HTML5. I do not think Steve Jobs will be unhappy about this at all.
-- Perhaps I see less than some, but more than many.
A certain sort of video (the kind you can't find on Youtube) comes primarily in Flash format. This sort of video seems to drive the adoption of new technology. If this can bring said video to the iPad, sales are certain to engorge.
A slashdotter who didn't build his own computer is like a Jedi who didn't build his own lightsaber.
This is fantastic news for Intel and AMD. Crap like this is why we need to buy a new computer with a faster processor every year, just to do the same shit we were able to do last year.
You know, I could watch streaming video just fine back in 1995 using RealPlayer on my old HP-UX workstation. That workstation probably has less computing power than a shitty clamshell phone today. But times change. Now it's 2010, and my computer from last year will barely have enough power to suitably run this JavaScript video player monstrosity.
It's not that we can do something that we couldn't do 15 years ago, it's just that we take an absolutely moronic approach these days.
Other than Apple's non-support of Flash on the iPad, this has nothing to do with Apple. This is an Adobe Flash emulator written in JavaScript.
I don't buy your take on things.
I think it has a lot more to do with being the gatekeepers for content (and continuing to get a cut of the profit) than with flash content itself. They don't want people using apps and games on their platform that you didn't buy from the app store, hence no Flash or Java on the i-devices.
Why should Adobe care? As far as their history goes, I think Adobe would love it if they didn't need to support a flash plug-in. They certainly don't seem to want to invest a lot of time/money into keeping it up-to-date.
Adobe makes their money on Flash development tools. They give the plug-ins away for free to sell more dev kits. I could see them kicking up a fuss over open source compilers, but not interpreters.
If apple was being honest about the reasons for not including flash, things like problems with sandboxing and concurrent app access etc, this probably inciodentally solves those problems so Steve may not actually care.
And it's a EULA btw.
I work for the Department of Redundancy Department.
Like others have said, you are confused about JS. It is a beautiful language that has been cursed by the browser. The only features I'd like to add would be (explicit) multi-threading, and typing beyond var. JS is a truly object oriented language that offers dynamic scoping and functions as first class objects. I understand there are some command-line interpreters that actually allow those, but I've only used it in the browser. If any of those languages you mentioned had made their introduction via the browser, you'd hate them equally or more so.
Comment removed based on user account deletion