Comments on: Flex Builder Linux Dead

By: heffer

heffer — Tue, 02 Jun 2009 04:59:16 +0000

It may come down to a money decision, however, if more linux developers had a tool like FlexBuilder, Adobe would have more browsers with their Flash runtime now wouldn’t they? This would ultimately be good competition for M$ and their SilverandGoldLight brand of Flash.

Don’t take FlexLinux away Adobe!

By: cferthorney

cferthorney — Thu, 21 May 2009 08:56:59 +0000

@sapphirecat – that community is not as small as you would think. Sure it is not huge, but you don’t have to use an outdated Eclipse version with the Alpha, and I think Adobe should leave it as such. FlexBuilder works OK with Eclipse 3.5M7 on Ubuntu 9.04. It boots and behaves in the same way as FB does on other Eclipse versions on Linux

http://bugs.adobe.com/jira/browse/FB-19053 is the Adobe bug for this – please vote for it.

By: max

max — Sat, 16 May 2009 09:03:11 +0000

Feel like i must lament this decision.

I have been working with flex for the past two years on linux and have been eagerly waiting for flexbuilder.

Programming for a platform that offers you no debugging tools is not worth it.

This may mean goodbye to flex for me…

By: sapphirecat

sapphirecat — Fri, 08 May 2009 12:52:09 +0000

It seems to me that Java never really caught on on Linux, due in part to Sun’s restrictions on distributing it back in the day. Also, the more ideological camps wouldn’t touch Flex because it produces Flash, a largely proprietary and binary format that search engines (and the iPhone) can’t use.

The number of Linux users willing to get 350MB of packages (a JRE, an outdated Eclipse version, and the 178MB Flex plugin) in the right bit size and install them all by hand to develop for a format with such disadvantages must be small indeed.

By: TJ Downes

TJ Downes — Sat, 02 May 2009 00:28:56 +0000

When I first saw this news a few days ago I was a bit disappointed. however, given the low demand for the platform I feel it is the right decision. I’d prefer to have all resources on projects that Adobe feels are worthwhile and generate revenue for them.

Simply put, we don’t develop websites for the 1% (IE 5.5, Lynx, etc) crowd because it’s just not worth it. We put that effort into making the experience better for the majority. I am happy to see Adobe doing the same.