+1 Need 64bit support yesterday

Just out of interest, I do php, java and flex. Do you reccomend getting a bare bones Helios and then installing the Java,PDT stuff from the main update site? Then install FB4 plugin.

Why do we need a 64 bit plugin?

I've been using the 32 bit plugin on a 32 bit machine with a 32 bit Springsource Toolsuite as my Eclipse IDE.

On my new 64 bit setup, Adobe forced me to run my 64 bit Springsource Toolsuite version of Eclipse spearate from the 32 bit standalone FlexBuilder.  Turns out I want to edit a few simple XML and HTML files in my Flex project.  Surprise - Flexbuilder grants me a plain old text editor to do it with!  Well, ok, how hard can it be to go get an XML editor plugin into Flexbuilder? It's Eclipse after all.

So, I try to get the XML editor from http://download.eclipse.org/releases/helios=> Web, XML, Java EE Devlopment Tools=> Eclipse XML Editors and Tools.  Surprise! (See Below.) Dealing with this is just too far away from any productive work.  What I'd like is a 64 bit plugin that I can stick back in my 64 bit STS and get on with my work.

Cannot complete the install because of a conflicting dependency.
  Software being installed: Eclipse XML Editors and Tools 3.2.2.v201008170029-7H7AFUQDxumQGOpBqffOY2f1qxDZ (org.eclipse.wst.xml_ui.feature.feature.group 3.2.2.v201008170029-7H7AFUQDxumQGOpBqffOY2f1qxDZ)
  Software currently installed: Adobe Flash Builder 4.0.1 (com.adobe.flexbuilder.standalone.product 4.0.1)
  Only one of the following can be installed at once:
    Eclipse Jobs Mechanism 3.4.100.v20090429-1800 (org.eclipse.core.jobs 3.4.100.v20090429-1800)
    Eclipse Jobs Mechanism 3.5.0.v20100515 (org.eclipse.core.jobs 3.5.0.v20100515)
    Eclipse Jobs Mechanism 3.5.1.R36x_v20100824 (org.eclipse.core.jobs 3.5.1.R36x_v20100824)
  Cannot satisfy dependency:
    From: Adobe Flash Builder 4.0.1 (com.adobe.flexbuilder.standalone.product 4.0.1)
    To: org.eclipse.rcp.feature.group [3.5.1.R35x_v20090811-9SA0FxVFqE70OL1ARMrfcO6e7BA6]
  Cannot satisfy dependency:
    From: Eclipse RCP 3.5.1.R35x_v20090811-9SA0FxVFqE70OL1ARMrfcO6e7BA6 (org.eclipse.rcp.feature.group 3.5.1.R35x_v20090811-9SA0FxVFqE70OL1ARMrfcO6e7BA6)
    To: org.eclipse.core.jobs [3.4.100.v20090429-1800]
  Cannot satisfy dependency:
    From: Structured Source Model 1.1.502.v201008311901 (org.eclipse.wst.sse.core 1.1.502.v201008311901)
    To: bundle org.eclipse.core.jobs [3.5.0,4.0.0)
  Cannot satisfy dependency:
    From: WST XML Core 3.2.2.v201008170029-7C7OFXYF7RZHQHI5PyJwPT (org.eclipse.wst.xml_core.feature.feature.group 3.2.2.v201008170029-7C7OFXYF7RZHQHI5PyJwPT)
    To: org.eclipse.wst.sse.core [1.1.502.v201008311901]
  Cannot satisfy dependency:
    From: Eclipse XML Editors and Tools 3.2.2.v201008170029-7H7AFUQDxumQGOpBqffOY2f1qxDZ (org.eclipse.wst.xml_ui.feature.feature.group 3.2.2.v201008170029-7H7AFUQDxumQGOpBqffOY2f1qxDZ)
    To: org.eclipse.wst.xml_core.feature.feature.group [3.2.2.v201008170029-7C7OFXYF7RZHQHI5PyJwPT]

Cannot satisfy ... customers?

+1 for 64bit support.

if adobe wants to remain competitive as a player in the digital era we are living in, it needs to do more than just stay current, they need to stay ahead of the times. we need hardware accelleration, we need updates and enhancements to the language, to the IDE, we need it now now now.

i++;

// Thanks!

+1 vote

PLEAAAAAASE!!!!!!!

Here is Flex JIRA entry.

https://bugs.adobe.com/jira/browse/FB-10052

Let's vote this!!

Shigeru Nakagaki

throw my +1 in the hat too. Argh.

+1 for 64bit support

actually we need it for all our devs in the office so +6!

Still not enough demand?

+1 for 64bit support.

+1 for a 64 bit version.

Adobe, seriously not cool.

I mean, come on!

We live in an age of openness.

How can Adobe claim to be competitive/compliant/advanced if it does not join the rest of the world? windows 64 bit is years old now, and so is Java and eclipse.

This is just classic Adobe mentality, and is what's threatening it's downfall, due to the widely agreed supremacy of things like JQuery and HTML5. Not because they are better, but because they adhere to standards, their power is in collaboration with technologies, not from enforcing them!

You can not live in a bubble and still be competitive. You are not stable if you just say you are while blaming your developers and not advanced if others are way past you in conforming to advances in technology.

What I see here are people begging Adobe to let them be their customers, and a bunch of excuses for what should be a non-issue.

People are saying they need the extra kick that 64-but provides, and they get answered that their projects should not be this large, or that they should use less plugins?

if you want to talk to Java, you should speek it's language. That of community, openness, and technological progress.

And don't even get me started on the support for 64-bit linux...

but I guess, to paraphrase google chrome's crash report:

THE FOLLOWING TECHNOLOGY HAS BECOME UNRESPONSIVE: ADOBE FLEX

+1 for 64-bit support as well.

Hi Andrew-

Thanks for the prompt reply to my comment; it is greatly appreciated. It is definitely encouraging to know a 64-bit version is, at the very least, on the horizon. Again, I hope my comments were not taken to be inflammatory or overly critical. My intention was merely to convey that this is becoming more of an issue and a pain point for developers who are investing resources in and committing to the Flash Platform, as a whole. As long as there is some relief in sight for this issue in the near future, I'm sure a lot of folks will be much more at ease going forward. Thanks again for your response and best of luck to you and your team with the 64-bit release.

Sincerely,

Thomas Fowler

+100 votes (1 for each developer in our organization)

+1 for x64 support!

Our team is consistently working with large Flex/Air applications that integrate with many other backend technologies. Unfortunately, the memory limitations of 32 bit eclipse installations are a severely limiting factor when we are trying to work on the entirety of the project within a single workspace. Furthermore, the memory profiler in Flash Builder quickly becomes unusable during large application development because it can't get the resources it needs to run effectively.

Please, Adobe, hear our cries! Give us FlashBuilder x64!

-Matt

P.S. Please also explain the current limitations to delivering one.

Note that the FlashBuilder is an eclipse plugin and eclipse itself is OS independant (as long as SWT is supported on the platform).

On the other hand linux support has been dropped as of AIR 2.6 - so the only supported (desktop) platforms are Windows and Mac OS.

And of course there is an x64 version of eclipse as well as an x64 edition of the JRE available, which is not the case for AIR or flash in general.

I think i will adobt IWantToLikeAdobe's google chrome quote as my signature on this forums:

THE FOLLOWING TECHNOLOGY HAS BECOME UNRESPONSIVE: ADOBE FLEX

Shame on you, Adobe!