🚀 go-pugleaf

    I would imagine a Taligent Based Framework, would have a lot in common with
MacApp (considering where many of the people came from)... the difference
probably being that the OS (and its routines) are optimized for the framework
(or are part of the framework itself). So this is where I want to be.... when
it becomes availible... and of course there will be a couple of years lag time
until the new computer/OS is accepted at large.
 
    The toughest part OOP is all the lost productivity. Yes, MacApp is saving
me time over traditional procedural developement... and it has sheltered me
from the toolbox (somewhat)... now I get to spend my time figuring out how the
framework wants something done, instead of how the toolbox wants something
done... and when I go to a different framework I get to learn it over again. I
have gained productivity short term, and been given a taste of the future...
but like giving a starving child a single meal, what about tommorow?
 
    There is Component Workshop, which I hear from everyone is great... except,
it is too damn pricey for the average small developer. Which (to me) means it
is unlikely to be accepted as a standard. And if it isn't likely to become a
standard, why would I spend my time learning an environment that wont help my
Resume? And this also brings up the question about how long the company will be
around (do we really need another proprietary, high priced development
environment, even if it is really good?)... Instead of trying to grab market
share the company is trying to make money off a first generation, unproven,
product... good luck... I sincerely hope they have good V.C.
 
    MacApp... apple has let the ball drop on 2.0 (no support, or good
translation tools)...  we hear the same for 3.0... but its O.K. because we have
Bedrock (Yet another framework). At least this framework is cross platform, so
it will look good on a resume, and there is a chance that the development
environment will be easy to work with. Think-Environments are easy(er) to work
with than MPW. (MPW is fine, but just a tad archaic... ObjectMaster is good
editing, but is not an integrated environmnent... and many things, like
renaming a method are still an impossibility (more work than its worth).) Of
course Bedrock is not optimized for Macintosh/Toolbox, nor is it optimized for
an OOP based OS... and things us OOP developers need, like; dynamic linking,
auto-magic memory/object managment, source code, and cheap licensing fees, and
a low cost environmnet... are still a huge '?'
 
    But we should wear peril sensitive sunglassed (the kind that turn black
when danger is near, so we dont have to see it)... Dont look towards tommorow,
face the day, and be thankful for the OOP tools you've got.
 
 
    Dave Every.