How did Apple Maker Project and Interface builders?
How did Apple make the Project and Interface builders if Application are made from those. Did they write one piece of code, and then use that to make the other part of the program, which in turn made another program?
Is the idea of a person making themselves out of nothing but....nothing?
ANSWERS?! <img src="graemlins/smokin.gif" border="0" alt="[Chilling]" />
Is the idea of a person making themselves out of nothing but....nothing?
ANSWERS?! <img src="graemlins/smokin.gif" border="0" alt="[Chilling]" />
Comments
NeXT did.
But yeah, the first gen of them was written in just code. There's nothing keeping you from writing a Cocoa app purely programmatically, so they wrote a minimalist IB, used that to whip up the next IB, which let them make a more complex IB...
It's the same principle behind compilers.
If all binary executables come from compilers, and compilers are binary executables... where did the first compiler come from? (It's called bootstrapping...)
sounds saucy.....
Any who, so, it was an asexual evolution?
This is a really powerful concept in tool development and software in particular.
If you can grab onto this concept of building tools, and then building bigger and better tools with those tools...watch out!
In addition, did you know that Project Builder is just a fancy frontend to some CLI apps? Run top while you're compiling in PB and you'll see a bunch of extra processes spring up.
Anyway, another funny thing about the compiler building compiler concept...
gcc 3.1 will generate faster PowerPC code than gcc 2.9.5 which is currently available.
if apple uses gcc 2.9.5 to compile gcc 3.1, they can use the newly compiled gcc 3.1 to re-compile itself and generate a faster executable!
BTW, I'm pretty sure gcc 3.1 was included in the most recent downloadable dev tools.