3 ms·

Does anyone here use this and have a recommendation on platform? My preference is Linux, MaxOS and Windows (in that order). But if not all platforms work equa

Does anyone here use this and have a recommendation on platform? My preference is Linux, MaxOS and Windows (in that order). But if not all platforms work equally well, I may reconsider.

javanix 16y ago
I don't have any first hand experience with it but it looks like the Linux version is running through Wine, not a native port. Wine is great but for 3D stuff (including games) I've found that its usually more trouble than its worth to get it configured right for my specific systems.
kikibobo69 16y ago
I noticed it does 64 bit only on Windows. Not a good sign for other platforms.
- georgemcbay 16y ago
  Adobe's CS products were 64-bit only on Windows for a while as well, due to Apple's last minute decision to drop 64-bit support for Carbon and force developers into Cocoa use for 64-bit apps. While Adobe addressed the situation with CS5, not every company out there has the same resources available for such a rewrite of their Mac-specific layer on multiplatform software. tl;dr -- Apple is at least partially to blame for the slow move to 64-bit apps on the Mac platform.
  - nika 16y ago
    This app is not written for the mac using Carbon or Cocoa, it is using Crossover. It is a windows app and they're using technology (wine for linux) to get it to run on other platforms. I don't think that, after creating carbon and delaying OS X in the first place due to the demands of microsoft and adobe, that Apple should feel at all guilty, when those two companies do not keep their promises to migrate to cocoa after nearly 10 years. This is especially heinous given that cocoa is a much better platform, is relatively easy to work with, and if the underlying code was written at all decently, the migrating should not be very difficult at all-- maybe a year of effort while working on the next version, and that's being generous. And as a result of doing that migration, even back in 2000-2002, they would have gotten more stable, better performant apps. They just couldn't be bothered, and so for that entire decade from Microsoft and Adobe we've gotten clunky, crappy apps that just have more features piled onto them every year. "64-bit" is just one of those features. Apple create carbon to soften the transition for these two companies... but they never bothered to transition. Further, Apple didn't drop 64 bit support for carbon, it never existed. This phrasing is one of the lies adobe has told about apple in their ongoing war. 64-bit carbon support was on a roadmap at one point, but they decided not to do it because the original mac OS X and consequently carbon are fundamentally 32 bit and it involved too many resources. I'm sure they did some exploratory work, but the claim that they "dropped it" is a claim that they shipped it and then reneged. That adobe has been able to lie about this and create an impression in you, and many others, that apple dropped support and "forced" people is one of the reasons Apple is so reticent to talk about future plans. That people are blaming Apple for this when Adobe and Microsoft sat on their asses for a decade, I just don't understand. (Well, actually I do.)

Does anyone here use this and have a recommendation on platform? My preference is Linux, MaxOS and Windows (in that order). But if not all platforms work equally well, I may reconsider.

javanix 16y ago

I don't have any first hand experience with it but it looks like the Linux version is running through Wine, not a native port. Wine is great but for 3D stuff (including games) I've found that its usually more trouble than its worth to get it configured right for my specific systems.

kikibobo69 16y ago

I noticed it does 64 bit only on Windows. Not a good sign for other platforms.

georgemcbay 16y ago
Adobe's CS products were 64-bit only on Windows for a while as well, due to Apple's last minute decision to drop 64-bit support for Carbon and force developers into Cocoa use for 64-bit apps. While Adobe addressed the situation with CS5, not every company out there has the same resources available for such a rewrite of their Mac-specific layer on multiplatform software. tl;dr -- Apple is at least partially to blame for the slow move to 64-bit apps on the Mac platform.
- nika 16y ago
  This app is not written for the mac using Carbon or Cocoa, it is using Crossover. It is a windows app and they're using technology (wine for linux) to get it to run on other platforms. I don't think that, after creating carbon and delaying OS X in the first place due to the demands of microsoft and adobe, that Apple should feel at all guilty, when those two companies do not keep their promises to migrate to cocoa after nearly 10 years. This is especially heinous given that cocoa is a much better platform, is relatively easy to work with, and if the underlying code was written at all decently, the migrating should not be very difficult at all-- maybe a year of effort while working on the next version, and that's being generous. And as a result of doing that migration, even back in 2000-2002, they would have gotten more stable, better performant apps. They just couldn't be bothered, and so for that entire decade from Microsoft and Adobe we've gotten clunky, crappy apps that just have more features piled onto them every year. "64-bit" is just one of those features. Apple create carbon to soften the transition for these two companies... but they never bothered to transition. Further, Apple didn't drop 64 bit support for carbon, it never existed. This phrasing is one of the lies adobe has told about apple in their ongoing war. 64-bit carbon support was on a roadmap at one point, but they decided not to do it because the original mac OS X and consequently carbon are fundamentally 32 bit and it involved too many resources. I'm sure they did some exploratory work, but the claim that they "dropped it" is a claim that they shipped it and then reneged. That adobe has been able to lie about this and create an impression in you, and many others, that apple dropped support and "forced" people is one of the reasons Apple is so reticent to talk about future plans. That people are blaming Apple for this when Adobe and Microsoft sat on their asses for a decade, I just don't understand. (Well, actually I do.)