Archive of UserLand's first discussion group, started October 5, 1998.
Re: OS upgrades (was: WINE ~= Carbon?)
Author: Nicholas Riley Posted: 4/29/1999; 7:41:20 AM Topic: Linux' wide open spaces Msg #: 5414 (In response to 5405) Prev/Next: 5413 / 5415
You're right about the 7.0 upgrade, of course, the same thing happened to everyone.
In OS X, Apple is taking the same approach Microsoft did with the 3.x -> 95/NT transition. The Blue Box works like Windows' 16-bit compatibility system, proving a virtual machine for old apps to run in, more or less at full speed, protected from the new ones, but not as much from each other. For writing new apps or porting them to run under OS X natively, you have four choices, more or less attractive depending on where you're coming from:
- If you have a unix/linux source base, do a straightforward port/recompile, it'll probably run, not pretty, but quite compatible. Add a GUI if you want via any of the other methods.
- Carbonize your Mac OS source base, requiring some small or large changes depending on how you wrote your program. It'll still run on "classic" Mac OS this way, via CarbonLib.
- Write it with the Yellow Box frameworks under Objective C, Java, or several other languages, you get a Windows runtime for free.
- Write in 100% Java. It's slow and memory-hogging but it might work for your program, and it'll run on almost every modern platform with a certain amount of debugging.
This is just complicated enough that it's hard for a lot of people to get. When I try to explain it to non-programmers, it takes too long. The message definitely needs to be simpler.
There are responses to this message:
- Re: OS upgrades (was: WINE ~= Carbon?), Dave Winer, 4/29/1999; 8:44:36 AM
This page was archived on 6/13/2001; 4:49:37 PM.
© Copyright 1998-2001 UserLand Software, Inc.