I run 32-bit Linux but there is a very vocal group of people who really want 64-bit Linux support for Flash Player. Today there is a decent work around for running the 32-bit Flash Player on a 64-bit Linux system using the nspluginwrapper. From what I’ve heard it works fairly well on most distro’s but I haven’t heard yet how well it works with the new Flash Player 10 beta. Despite this potential work around eventually Adobe does need to natively support 64-bit Linux – and they will. This is not as simple as a recompile – otherwise there would be 64-bit support today. There is a bug already filed in the public Flash Player bug database for 64-bit support. I’d encourage you to not just go vote for that bug but also to get involved. As Tinic Uro points out in the bug comments, the missing piece for 64-bit support is open source – so you can help! Flash Player uses the open source Mozilla Tamarin VM. This VM does not yet support 64-bit Linux because all that machine code generation in the JIT compiler needs to be ported from 32-bit to 64-bit. The code is in Mozilla’s Tamarin Central Mercurial repo. This IS open source! You can help get 64-bit Linux support for Flash Player!
Tomorrow night I’ll be presenting at the New York GNU/Linux Meetup Group about Adobe Open Source – including the Adobe Flex SDK, Mozilla Tamarin, Adobe AIR (pieces like SQLite and WebKit), and BlazeDS. More details here. Hope to see you there!
That’s 1,117,019 more reasons you can Count on Flex!
“Count on Flex” is a series of blogs about the current state of the Flex ecosystem… by the numbers.
For this post I did a very basic calculation which doesn’t factor out comments and licenses. For the Flex SDK and BlazeDS I used this command:
find . \( -name "*.java" -or -name "*.as" -or -name "*.mxml" -or -name "*.css" \)|xargs wc -l
And for the two Tamarin projects I used this command:
find . \( -name "*.py" -or -name "*.as" -or -name "*.cpp" -or -name "*.h" -or -name "*.es" \)|xargs wc -l