CompuServe Messages

#Mac/Win crosspltform Dev

    12-Mar-94 11:09:45
Sb: #163477-#Mac/Win crosspltform Dev
Fm: David F. Johnson 71301,3334
To: Neil Ticktin/MacTech Mag 71333,1065
Again, I find you misrepresenting Microsoft and, this time, adding Windows development. I have been programming professionally on the Macintosh for five years with a wide variety of tools (MPW Assembly/C/C++/Pascal, THINK C/C++/Pascal, the TCL, MacApp, AppMaker, HyperCard/SuperCard, The Debugger, and more) for an incredibly wide variety of software solutions (LDEF, WDEF, and the whole DEF family, INITs, cdevs, rdevs, applications, externals, databases, networking, and more). Early last year I "broke thru Windows" by writing several import and export DLLs for CorelMOVE (part of CorelDRAW). This is what _I_ found to be the truth: 1) I don't need Jasik's debugger to debug non-application software — CodeView will provide source level debugging for me. 2) I don't need to ask Microsoft any questions — their online help system is exhaustive, and their sample code is practical and useful. 3) Windows doesn't go down when my application does — proper use of protected memory (though, admittedly, not perfect). 4) MSVC is a better development tool than anything available on the Mac — and MFC is getting better and better (not designed nor implemented by one person, like the TCL and Power Plant). 5) The Windows API better facilitates "hooks" into which I can provide customized features — no need for trap patches. 6) Windows' windows provide a natural "view" hierarchy which helps when using non-object languages — no need for the MFC, MacApp, the TCL, or Power Plant. 7) Microsoft gives me more than I need on their "E.T.O." equivalent — I'm able to view any and all technologies with no problem. 8) I'm a better software engineer today because I now am competent on two platforms — go to the bookstore and compare the technologies exemplified in books and magazines in DOS/Windows research to that of Macintosh (there _is_ no comparison). 9) enough already! The biggest problem with Windows development is the memory model issue – which do you use? That is being addressed with Win32s, Win32c, Chicago, and, of course, NT. For Window 3.1 it's a necessary evil. By years' end this will be coming to a well deserved death. I love Macintosh. I like Windows. However, based on my experiences I'd rather program under Windows than the Macintosh, and I'm nearly as productive under both (with Windows being slightly lower due to a 5-to-1 ratio of experience). Just my opinion…