4 ms·
Adobe Flash to cross-compile code from C, C++, Java, Python, and Ruby to ActionScript
- wallflower 19y agoAdobe Flash is aiming to become the Applet of the 2000's. They very well might pull it off - except that Flash content is not discoverable by search engine crawlers (startup idea anyone?)
- stillmotion 19y agoA web spider that's run by out sourcing work to China. We could have hundreds of thousands people going to flash websites and entering the contents into a database. Would work flawlessly.
- staunch 19y agoMaybe you could just disassemble swfs and extract the text. I wonder why Google doesn't do that (or do they!?).
- thorax 19y agoSounds a lot like pressure from Silverlight's DLR allowance for multiple languages, doesn't it? If so, this is a good example of competition "waking-up" age-old platforms (like Flash).
- jcl 19y agoNo kidding. Consider that as of April 2005, a Flex license had a $29,000 price tag (I haven't been able to find more recent numbers): http://tech.groups.yahoo.com/group/flexcoders/message/12200 http://tech.groups.yahoo.com/group/flexcoders/message/12200 Then, two years later, they announced that the Flex SDK would be free and eventually open source: http://developers.slashdot.org/article.pl?sid=07/04/26/140241 http://developers.slashdot.org/article.pl?sid=07/04/26/14024... ...which was within a month after Microsoft released Silverlight.
- deleted 19y ago[deleted]
- wmf 19y agoFlex 1.x was a joke, but Flex Builder 2.0 was only $500. Making the Flex SDK (but not the IDE) open appears to be a case of openwashing, since most Flex developers are probably still buying the IDE.
- sakri 19y agoAs far as I can remember, Flex1 was a "server". This (I suppose)was an excuse for the outrageous price. Users would upload their MXML and AS files, then the server would spit out '.swf' files to client requests. A compiled swf was cached until new MXML or AS files were uploaded. It was a "one licence" per company approach, rather than one licence per developer one.
- dhouston 19y agoby "supporting" other languages they mean they can compile the interpreter's c/c++ source code using their LLVM->actionscript bridge (http://blog.digitalbackcountry.com/?p=1095 http://blog.digitalbackcountry.com/?p=1095) they came up with and then run the script on top of that actionscriptified interpreter. which, even for people like me who drink the interpreted-languages-are-fast-enough koolaid, seems like a lot of levels of indirection :) i think the CLR approach seems a little more straightforward: "native" interpreters that compile e.g. python->the CLR IL (instead of python->interpreter c source->llvm->actionscript). and i doubt you could just take e.g. the python interpreter and throw it into a SWF -- certainly pieces of the interpreter along with C modules that interact with the filesystem, etc. would need to be tweaked to deal with the AIR runtime. cool idea though, and they even got quake 1 (!) running in a SWF (see the video below in this thread... wild stuff)
- edw519 19y agoPerformance?
- wmf 19y agoSandboxed C/C++ bytecode? I'll believe it when I see it.
- ed 19y agoBelieve it. http://blip.tv/file/408241 http://blip.tv/file/408241 (It gets interesting at 4:50)
- bilbo0s 19y agoYou should pay closer attention. The game is a Far Cry (pun intended) from DirectX 10. The demo was also on a Windows machine. Let's see the same demo on Linux. The original poster is absolutely correct. C++ written for KDE is going to run on Windows now. Well, having worked at Adobe when I was just out of college, I can say that they have VERY bright people there. Bright enough to get C++ code written for Linux to run on Windows? in a VM? Which itself would be in a browser? I have to think that VMWare or Parallels would have done that already if it was doable. Or, if it is doable, and just hard, VMWare and Parallels will do it better than Adobe in any case. Be assured, with the value inherent in such a product they WOULD release their own versions. I can hear the Flash VM talking now: Scenario 1: Oh C++ code . . . you want me to run some Intel vectorized math routines? No problem . . . those Microsoft templates you got there are REALLY cool . . . uhh . . . well let me just get this Objective C library here on this shiny new MacBook Pro and . . . Oh Wait? . . . Well . . . Maybe I can try this GCC library and . . . SLASH!!! <Leopard kills Flash VM process, and drags carcass home to feed cubs.> Moral of the story: Predatory cats always target the slow ones. Scenario 2: Ahh C++ code . . . I get it now . . . you want to use this really cool GeForce 9xxx series card to do instancing. That is AWESOME!!! Let me get started on that for you . . . uh . . . ahh . . . OK so I'm an OpenGL context and you want me to make a DirectX call . . . Oh OK no problem . . . ahh . . . . umm . . . OK so I'm on Linux, can I ask a quick question? Your developer didn't supply you with a software DirectX 10 implementation did he? <C++ code makes sad realization that both developer AND Flash VM are idiots> Moral of the story: Even intelligent things, C++, can be put in situations where it looks really stupid. Scenario 3: Oh mapped memory? SURE, I'll just go over here to this pool of unused hard drive space and . . . THWOCK!!! THACK!!! WOCK!!! WHACK!!! <Flash VM realizes that VISTA is actually a Dominatrix, and he is now being beaten about the head, neck and chest with the interrupt controller he asked for.> Moral of the story: Something like unused hard drive space, or cross compilation, may sound REALLY good . . . but make sure you know who has a claim on it . . . because she might be a REAL bitch. Or worse . . . Microsoft. Scenario 4: Oh . . . multicore . . . umm . . . why don't I go ahead and kill myself now so you can get to the blue screen faster. <Single gunshot is heard from the other room, system hangs without getting to the bluescreen, because Flash VM had problems even managing to commit suicide. The bullet went through its brain, but its vital organs were untouched.> Moral of the story: Actually test claims before you start making plans, a lot of the potential technologies you want to use, or potential spouses you will meet, will make claims of intelligence, but there may not be too much between the ears.
- mullr 19y agoHm. This may make flash suddenly relevant to me and many others. Actionscript itself is weird, so I've avoided it. But python or ruby, that's workable. I wonder if they're going to do it at the bytecode level for java? That would open up a variety of other interesting languages. What I want to know is: what's the value of this to Adobe? It's been apparent for ages that they're trying to claim platform share. But I don't understand what this buys them. Sales of developer tools? That can't possibly be very much. I can imagine it being 'strategic', but I don't know how. Perhaps this is why I'm in a cubicle, not a boardroom. :)
- alaskamiller 19y agoactionscript is derivative of ECMAscript, it wasn't that hard to pick up
- deleted 19y ago[deleted]
- xtat 19y agohow about flash that I can run outside proprietary adobe players? This move is unimpressive, unsurprising and totally self-serving. It's goal is to suck more code into vendor-locked adobe space.
- nickb 19y agoHTML >> Flash. Personally, I absolutely LOATHE flash/flex only sites. They behave horribly on the usability side, lack simple stuff like 'back button' and text sizing, and they task/heat up the CPU like you wouldn't believe (especially on a Mac). Flash has a purpose on the web... you can use it for various widgets that are impossible to do in HTML (say, recording and playing video and playing back animations and audio). But I'd never use it as a general presentation layer.
- jcromartie 19y agoMaybe I'm missing something, but what's wrong with ActionScript? I've never used it, so I don't have much to go on besides the fact that it's based on ECMAScript/JavaScript. Being a superset of JS can hardly be considered a bad thing. You still get the prototypes, dynamism, and functional programming of JS with AS, right?
- maxwell 19y agoActionScript 3.0 is basically Java. We're using it at work, and, compared to JavaScript (with a good library), it's pretty uncomfortable. They've made it (optionally) classical and static. Prototypes, dynamism, and FP are pushed into the corner. It's really gross. The modularity seems kind of nice at first, but then you realize they wrote a bunch of mediocre libraries instead of building a good lang. At least it has E4X, which is very nice, but then, I've found JSON to often be the better approach anyway.