+1 for 64bit .. It's real pain to do any enterprise sized project - you'r loosing to other IDE's here ... no way anyone can justify all time crashes, deployment problems (which rather goes to WTP) and ultimatelly .. very poor maven support - where I don't really see another way of development then with continuous build based on maven

Our project is some 80 flex and 150+ java/groovy projects. The problem is, that what is being recognized as one of the most important features, is the possibility of continuous development/debugging process for UI to Backend code, within single IDE. That contributes quite a lot to the overall flow of developer's daily tasks. AS3/Flex is great stack for UI building, unfortunatelly, it is really difficult to make a case here if you are unable to integrate it into the factory of sw development. 64bit IDE + compiler would be great step ahead in this competition (but only leveling with the others atm).

Good luck

Very few developer machines still have less than 4GB Ram and the lack of support from Adobe shows a disinterest in Flex usage in a professional context. Together with the deprecation of Google's map API for flash and other major actors that will follow, I think the safest route is to abandon Flex development all together.

Andrew,

It looks like this has been going on for at least a year, now. You really do need to provide 64-bit support.

Can you at least release a 64-bit plugin, ASAP?

Have a great week.

Take care,

Darwin

+1 vote for Eclipse 3.7 64bit support (wow... that's one popular demand and it has been here for 17 months...)

At this point with HTML 5 and Adobe pretty much dropping Flash on mobile devices I personally no longer care whether there is a 64 bit version of the IDE as I will no longer be doing any Flash/Flex development. I'm sure it's still important to the rest of the community and I don't want to downplay that but for me it's an issue of too little too late. I'm sure I'm not alone

Hello,

Without wanting to be pessimistic or finger pointing I have to disagree on the "flex for ever" view. If you ask me the arrival of HTML5 put flex in a EOL state. The absent response by adobe to this thread, Adobe Muse and the arrival of simple tools provided by for example google to transcode flv to html5 says enough.

Not that I think HTML5 is THE future product to focus on. I' m more a believer of a "applications" web but I fear flex is a lost case by then. Sure maintenance will remain for those enterprise applications, but that is it.

@Majathi, that may be true to some extent as far as flex is concerned, BUT I don't think HTML5 is the technology to replace flex.  HTML5 from flex is a step backwards from a mature (albeit buggy) API to a very new and unproven one.  I also don't see whole enterprise applications being built in HTML5 any time soon.  like I said it's great for angry birds and bouncy balls...  but I'm not sure it is a VIABLE replacement for the FEATURES of flex.  I'm not debating that flex is facing EOL, but it's very far off.  FLASH on the otherhand is AT EOL.  I think that HTML5 will kill flash, but flex does not really have a viable replacement yet.

All my colleagues and I work with 64bit OS and we experienced performance and stability issues... I vote for 64bit Support!!

Thanks,

Mario

+1 for 64-bit FB4

We've hit the memory wall and this is becoming a serious issue.

+1 for 64bit support.

+1

+ 1 for FB 64 bit