Well, after what happened (or didn't happen) with the PowerPC, they may have decided to wait and be sure that whatever new path Apple was going to take was really going to stick, and work, and be accepted.

It is one thing for a huge corporation like MicroSoft to pour millions of dollars of development into a project and then realize that it is a dead-end street and pull the plug and never notice it in their bottom line, but it is quite a different thing for a small niche-market company like Coda (or Net4Music or MakeMusic or whatever they feel like calling themselves these days) to pour a lot of development money into a project only to find that it is going nowhere.

So the corporate bean-counters may have made the developers wait until OSX was really going to happen, was really adopted by the user-base and had all the major bugs and kinks ironed out before deciding to put the sort of money that such a major revision requires.

Who knows? Well, I'll bet that those that do know are not at liberty to say why they had to wait, but I will bet that the people doing the actual development would have loved to have gotten started on porting it to OSX long before they were allowed to.



Philip M. Aker wrote:
On Saturday, Jun 7, 2003, at 13:17 America/Vancouver, David W. Fenton wrote:

Nope. It's Coda not having had their ear to the ground 6 years ago when Apple sent out copious notes about coming changes.


[...]


I think that Code is following exactly the same path with OS X as they did with Win32, and my guess is that this involves a major code restructuring and maybe even a conversion to new development tools, > ...


I'll agree that a port takes time but other than that:

1. Should have learned from Windows port that they'd have to allow for that time.

2. They're still using CodeWarrior for Mac development.

3. They essentially let the Mac-specific code stagnate since the adaption to PowerPC (1995?) thereby exacerbating porting issues for OS X compatibility.

4. Misreading their own market, management made a deliberate decision NOT to invest in the Mac platform. That is to say it appears that the only function Mac programmers have at Coda is to port Windows code. This has serious repercussions because currently, the UI features are largely based on what someone who doesn't actually know or care about Macs "thinks" is possible to port from x86 target based on the 1993 era System 7 toolbox. What the hell? Today's typical Mac user has a far greater software experience she did 5 or 10 years years ago and isn't fooled so easily. That's the $US284,000 message from the Mac user community for lack of platform support. IMO, whoever at Coda has been making those kinds of decisions should resign and pay back the lost sales from their own pockets. This money will then be used to advance the Macintosh version to state of the art.


Philip Aker http://www.aker.ca


_______________________________________________ Finale mailing list [EMAIL PROTECTED] http://mail.shsu.edu/mailman/listinfo/finale

.



--
David H. Bailey
[EMAIL PROTECTED]

_______________________________________________
Finale mailing list
[EMAIL PROTECTED]
http://mail.shsu.edu/mailman/listinfo/finale

Reply via email to