have a look around the forums, you'd think that the new Intel iMacs are the only way to go and that any G4 and G5 chips are now obsolete.
Oh yes he did. Check post #153. Note the word "pirating".danielwsmithee said:No one said anything about piracy! Unless of course you think "buying" a copy on eBay is piracy?
SiliconAddict said:I've been involved with testing\porting our companies internal apps from Windows version to Windows version. While that hardly counts as a large project my main point was that there was/is a high probability that Adobe knew, not sure about Microsoft though, in advanced that Apple was migrating and I wouldn't be surprised if they were sent development kits about the same time Apples internal development started. My point is that Adobe and Microsoft aren't small companies. We aren't talking a development house of 5 people. If Adobe\Microsoft wanted to they could have at least beta versions of UB's out right now. Yes I'm aware that as a Carbon app a transition wouldn't be easy by any stretch of the imagination. But again with the resources available at such large companies it should be doable. And that was my overall point. Not that it would be easy but that these companies have the resources to plow ahead faster then others.
The question I have is realistically would an entire rewrite be necessary to get native x86 compatibility up and running on Adobes apps.
wnurse said:You are missing the point. Any sufficiently large corporation can port an application in seven months provided it has unlimited resources, example, hire all the developers in the U.S and have them porting application (an extreme example, i know).. my point is, why would adobe and microsoft, after being told about a june release date, set a deadline of january for their application porting?. Developers cost money. There is a reason that there was a deadline. So companies could plan their resources accordingly. Lets do a thought exercise. Before apple announced their intel switch, adobe developers were not just sitting around doing nothing. Apple announces their switch. Adobe has to move developers from whatever they were doing to port. They have to calculate how many developers to move to porting. Other projects may now have to work with less developers.. adobe then may have to hire additional developers. They have a deadline, they compute how many developers it would take to reach this deadline, they have to hire these developers (developers are not falling off a tree). Now, imagine you are managing your resources.. why would you go the the vp of the company and say, "hey, lets spend millions more money hiring more developers, moving even more developers from whatever project they were doing to porting so we can get this done earlier than apple is gonna release new software so it can just sit there on the shelf".. How do you think VP of finance is gonna look at that proposal?. I happen to be familiar with some financial decisions a company makes because my aunt owned her own company and i worked for her for a while.. now, maybe you are familiar too but you seem to think money grow on trees and a company would just for no reason at all, spend more money than is necessary. Now, would adobe have finished porting by June?.. probably not.. but asking them to port by january when they had no information that they should is kinda silly. Maybe they didn't even plan to complete porting by june anyway. Adobe is big but they do not have unlimited resources.
Neither would a new iMac (although the Mac Book Pro might have been a bit of a surprise)hayesk said:You mean the rumors that said the first Intel Macs would be a mac mini media centre and an iBook? Well, if I were Adobe, I wouldn't put the rush on for that.
Besides, it's not like adding twice the people to a project makes it take half the time. Think about what you are expecting here.
mongoos150 said:You can argue that differently in 6 months if/when great new "pro" Intel towers are released by Apple
I'd consider myself a creative pro, using FCP and Adobe CS (I'm a media arts student), and the new iMac is suiting me far better than my PowerBook. The new iMac is on par - and surpasses most - pro machines. It's absolutely a pro-capable machine.gregarious119 said:That's my point though. I wasn't trying to compare the MBP to the new iMac...I know that desktop machines almost always will beat a comparable laptop. My point was that we've got people complaining about Pro apps being slower and even not compatible (like FCP) on these brand new iMacs (maybe I wasn't catching the bigger picture of the rest of the thread). None of this Intel stuff was supposed to be out until June anyway, so lets give it some time, wait for Apple to get their "pro" desktops working, let the pro software come along with it, and let those creative pro's go out and do their thing.
mongoos150 said:I'd consider myself a creative pro, using FCP and Adobe CS (I'm a media arts student), and the new iMac is suiting me far better than my PowerBook. The new iMac is on par - and surpasses most - pro machines. It's absolutely a pro-capable machine.
mongoos150 said:I'd consider myself a creative pro, using FCP and Adobe CS (I'm a media arts student), and the new iMac is suiting me far better than my PowerBook. The new iMac is on par - and surpasses most - pro machines. It's absolutely a pro-capable machine.
cr2sh said:Sales might be sluggish.. but I'm not sure why.
wnurse said:You are missing the point. Any sufficiently large corporation can port an application in seven months provided it has unlimited resources...
Norse Son said:MacOS X has been out for 5 years now. Developers knew back then that Carbon apps "would suffice" to work in the MacOS X environment, but Cocoa was the future. It's somewhat... hmm... "pure laziness" on their parts if they hadn't already transititioned their apps to Cocoa.
gregarious119 said:That's my point though. I wasn't trying to compare the MBP to the new iMac...I know that desktop machines almost always will beat a comparable laptop. My point was that we've got people complaining about Pro apps being slower and even not compatible (like FCP) on these brand new iMacs (maybe I wasn't catching the bigger picture of the rest of the thread). None of this Intel stuff was supposed to be out until June anyway, so lets give it some time, wait for Apple to get their "pro" desktops working, let the pro software come along with it, and let those creative pro's go out and do their thing.
gnasher729 said:No matter whether Apple told developers to move from CodeWarrior to XCode or not: CodeWarrior is dead. Ron has left the building.
Adobe is going to run into serious trouble with Photoshop quite soon, because there is no development system for sale anywhere that lets you build Photoshop plugins anymore.
Edge100 said:I'll just wait until Logic, Live, Reason, etc are Intel-ready.
Edge100 said:That is precisely why there is no software, and why Apple didnt release "pro" machines. The pro machines will be here when Logic, FCP, Photoshop, etc are Universal.
Edge100 said:That is precisely why there is no software, and why Apple didnt release "pro" machines. The pro machines will be here when Logic, FCP, Photoshop, etc are Universal.
daveslc said:And when Rosetta does Classic.
Just use http://www.gibix.net/projects/sheepshaver/ (no idea how well it works, but apparently it works on Intels)daveslc said:And when Rosetta does Classic.
bugfaceuk said:I seriously doubt Adobe have not been kept in the loop. MS may be a different proposition. From Adobe's perspective I think the early release of the Intel Macs is almost irrelevant. Their app runs under Rosetta with a "pro-spec" machine (i.e. enough memory) it runs well enough for amateurs and semi-pro.
Adobe as a large company will probably have taken this as an oppertunity to consolidate (shared code/build processes between windows/osx development), and look for additional savings that will deliver over the long term. Backed with if one of their customers really needs to run one of their apps, they can. When's CS3 due out? I would not be stunned if it wasn't UB until then. Why would they?
Companies often spend more money than they "need" to right now, in order to gain benefits in the future (we've just re-architected our 10 year old product from the ground up, it's taken time and a lot of resource, but it is now delivering benefits every single day. We didn't have to do, but the business justification for spending now in order to be more agile and efficient later was strong).
Anyway, I seriously doubt this was presented as a porting project to the CFO, much more likely as an integration and consolidation++ project. The reason we don't have an UB Adobe suite today is that they don't see the need to be native intel today. They could have done it if they had wanted to, and finance was probably not the reason they didnt'.
Their app runs under Rosetta with a "pro-spec" machine (i.e. enough memory) it runs well enough for amateurs and semi-pro.