[info-mcl] MCL Past vs. Future

[Pascal Costanza]

On 16 Oct 2007, at 21:44, Lyman Taylor wrote:

>
>
>   A couple of points.
>
>   1. A "future" MCL could have an insanely great Cocoa interface  
> but if there isn't
>      a sustainable community of developers using it, that's  not a  
> sufficient
>      for sustainability.
>
>      The appeal to going with Eclispse was to grow the commmunity of
>      developers by giving them a development/IDE that they will  
> more quickly
>      accept.  I saw *NO* intent that would be an end-all of what  
> was being
>      developed. ( yeah, yeah ... eat your own dog food would be  
> nice; a Lisp
>      IDE in Cocoa. Pragmatically though, Macintosh specific Common  
> Lisp is a
>      niche market of a niche market of a niche market.
>      How many Mac only software tool vendors are there out there?
>      Now highly successful Mac only software tool vendors?  
> Codewarrior? gone.  )
>      [ if there is denial going on it is on how generic the  
> usefulness of
>        embeddend and IDE editor into a finished application is. ]
>
>
>     Eclipse is on top of Java which leverages Cocoa. That Java/ 
> Cocoa work is done
>     by Apple. What is the likelihood that Apple is going to drop  
> supporting Java
>     directly?????    So how is leveraging a Java platform  that not  
> aligned with
>     Apple's objectives???

Apple have dropped all kinds of things in the past - even complete  
operating systems. So why shouldn't they drop Java? Java is not vital  
to Apple. They haven't included Java on the iPhone, that's already a  
strong sign of their disinterest in continuing support for Java.

Personally, I think that Eclipse sucks big time. But that's just a  
personal opinion.


Pascal

-- 
Pascal Costanza, mailto:pc at p-cos.net, http://p-cos.net
Vrije Universiteit Brussel, Programming Technology Lab
Pleinlaan 2, B-1050 Brussel, Belgium