 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Mac Forum / Programming / CodeWarrior / May 2005Why is CW Pro 9 temporarily unavailable?
Sorry if I missed a posted answer to this, but I didn't see one when I looked. Larry > Sorry if I missed a posted answer to this, but I didn't see one when I > looked. They're making sure that the CDs don't have any vestiges of the Windows products, which they don't own any more. >Sorry if I missed a posted answer to this, but I didn't see one when I >looked. > >Larry James answered correctly. We had to remove any of the x86 technology and this involves more than just removing the compilers/ linkers and libs etc. For example the debugger might have something in it that is considered x86 technology even it if is only hosted on Mac. Ron  SignatureMetrowerks Community Forum is a free online resource for developers to discuss CodeWarrior topics with other users and Metrowerks' staff -- http://www.metrowerks.com/community -- Ron Liechty - MWRon@metrowerks.com - http://www.metrowerks.com I really sorry to hear that you've sold off the Windows side of CW. It seems to me that the ability to use CW for cross-platform work would be added incentive for choosing CW over Xcode. Was that not considered to be the case in practice? Larry >> I really sorry to hear that you've sold off the Windows side of CW. >> It seems to me that the ability to use CW for cross-platform work >> wwould be added incentive for choosing CW over Xcode. Was >> that not considered to be the case in practice? Well, I doubt that it was even considered at all. I am guessing some Freescale bean counter simply looked at the Windows hosted tools, saw that the ratio of development costs over sales was unattractive and decided to sell it all, without giving any consideration to the fact that many of the remaining Metrowerks Mac customers continue to use CodeWarrior because it has the x86 cross-compiler. Certainly not all, but a sizeable chunk of us. By getting rid of the x86 cross-compiler, Metrowerks has unwittingly cut its own throat by removing one of the few key advantages CodeWarrior still had left over Xcode. An equally brain-dead move would be for Metrowerks to discontinue CFM support in CW 10. I have been a long-time CodeWarrior fan, having been a beta-tester way back in '93 (before it was even called CodeWarrior). I have been a big supporter and it has remained my preferred development environment, even to this day with CodeWarrior 9.4. It is a bit frustrating though watching Metrowerks find ways to make me jump to Xcode, dropping cross-compilation little by little, adding annoying registration files, pulling no-shows at WWDC, etc. Hell, if Metrowerks would simply put out an updated version of CW Pro 8.3 for Mac & Windows which was compatible with Tiger, I'd use that and nothing else! As Metrowerks finds more and more ways to drive away its customer base, it's become depressing. It used to be that virtually every other Mac developer I knew was on CodeWarrior; now, I am the only one I know left who still uses it as the primary compiler. Metrowerks' snubbing Mac developers by refusing even to make a polite appearance at the last WWDC was the final nail in the coffin for most of my colleagues. And now, CodeWarrior itself is being suspended from sales for some indefinite period until the remaining x86 technology is lobotomized out. Does anyone at Freescale even notice or care about the Mac market? MWRon seems to be the only voice left with the original spirit of Metrowerks. Can this be the same company that was so customer-driven only a just few years ago? Is this the same Metrowerks which inspired developers with every new release of the exciting new technologies available? Do these apathetic Freescale ringleaders even understand what they are hiers to? Depressingly, Jonathan Hoyle Eastman Kodak >Can this be the same company that was so customer-driven only a just >few years ago? Is this the same Metrowerks which inspired developers >with every new release of the exciting new technologies available? Do >these apathetic Freescale ringleaders even understand what they are >hiers to? Hello! If the state of events hasn't been clear to you since about the release of Mac OS X DP4 in mid 2000, then I don't know what to say. The G5, the currently quintessential Apple product, where all the high-end third party applications should be focusing, as new hardware drives their software revenue, still isn't supported by MW nearly 2 years after its release. The G5 isn't even 'high-end' anymore. Apple has migrated it into its entry level consumer iMac! I believe this alone should deeply concern MW remaining customers. This affects your products' ability to reach the people who are paying significant amounts for new hardware and want to pay to get software that takes advantage of their hardware investment. MW's tools currently don't give you this ability. Apple's tools have since the technologies initial release. In my opinion, a 3rd party would sell more Mach-O G5 capable applications that CFM based Mac OS 9 applications. Of course, this can vary from market to market. Any market that is running Mac OS 9 CFM applications obviously isn't buying new G5 powerhouses. But they probably aren't buying many new applications either. MW's new releases have less features than the previous one. Apple's have more features than the previous one. I would hope that it is apparent that the curve suggests that using Apple's technologies is the better choice for 3rd party software to use. No, it's not so apparent yet. Don't be so naive as to think that Xcode is the greatest thing since sliced bread. Xcode most definitely has its share of warts. Apple does seem to be improving it a lot, and that may be the result nothing more than the fact that Xcode is what Apple uses internally. However, I have some concerns: - I've never like using Apple's development tools, primarily I think because they lack an elegant UI. I am a Mac *user* as well as a Mac developer, and I prefer a GUI development environment to the kind of things Apple as always given us. I've played with Xcode, and just didn't like it. - I never know what Apple's going to do next, what it will support, what it will allow to languish (not that MW has done much better in the past few years). Interface Builder is another Apple tool, arguably even more essential than Xcode for Mac OS X development, and IB is the buggiest, most brain dead tool I've ever used since I started writing Mac software almost 15 years ago. - Apple is always clearly focused on the current version of Mac OS X. Don't ever expect to use the latest features in Xcode in an older version of Mac OS X. Don't expect to get bug fixes if you aren't using the latest version of Mac OS X, and don't expect support if you need to support an older version of the OS. - Competition is a good thing. If CW goes away, we're all at Apple's mercy and that doesn't give me a very comfortable feeling. Regarding G5 support, I know CW needs it, but for most of us I think it's overrated. The reality is that most applications spend the majority of their time waiting for user input. Do nothing with 64 bits isn't really any faster than doing nothing with 32 bits. Larry > - I've never like using Apple's development tools, primarily I think > because they lack an elegant UI. I am a Mac *user* as well as a Mac > developer, and I prefer a GUI development environment to the kind of > things Apple as always given us. I've played with Xcode, and just > didn't like it. Sheesh, they can't even get drag & drop right in the text editor. Using Xcode feels like using some crappy Java/Linux app. However... |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.