Re: Cocoa/EOF for non-enterprise apps Re: proof of cocoa
Re: Cocoa/EOF for non-enterprise apps Re: proof of cocoa
- Subject: Re: Cocoa/EOF for non-enterprise apps Re: proof of cocoa
- From: Deirdre Saoirse Moen <email@hidden>
- Date: Mon, 18 Jun 2001 12:33:42 -0700
At 10:23 AM -0400 6/18/01, Bill Bumgarner wrote:
Why do you justify Apple's position? Is it some great reaffirmation
that CodeFab is doing the right thing ? That everyone who trusted
Apple about YB/Windows and EOF/ObjC are idiots who deserve to
crash&burn? I don't
get it. Yea, you can justify anything, but that doesn't stop
reality, and reality is that Apple is burning bridges.
I am trying to convey the message that EOF/ObjC is end of life'd for
a variety of reasons that are more valid than "Apple is trying to
screw its customers". ....that EOF/Java is a lot more viable and
pleasant to work with than a lot of folks have assumed.
But not suitable for horizontal market apps, where EOF/ObjC would be.
A couple of people have conjectured that building a JDBC adaptor
that speaks across the bridge to ObjC/EOF would be a viable solution.
It might very well be, but there are some significant engineering challenges.
Not really. Most JDBC support isn't written in Java. This should be
intuitively obvious. ;)
It would help support those that want to port from EOF/ObjC to
EOF/Java, but it sounds like most of the folks in the EOF/ObjC camp
want to stay there and Apple would likely face this same issue again
in a couple of years when they really wanted to end-of-life EOF/ObjC.
So, you're saying they broke the EO palette because they wanted to
end-of-life EOF/ObjC?
Ah well, you're not responding, but it does rather contradict what
you'd said earlier. Nevermind. :)
That's that. I'm done. Have code to write; ObjC, Python, and Java,
Well, I'm now employed, so I'll keep this shorter. :)
--
_Deirdre Stash-o-Matic:
http://weirdre.com http://deirdre.net
"Cannot run out of time.... Is infinite time. You... are finite....
Zathrus... is finite. This... is wrong tool!" -- Zathrus