Herbie and all, Herbie has offered some interesting ideas and prejudices (Dated: Thu, 23 Jul 2009 10:42:05 +0200): > ... there is no future for non-OO languages on > the Mac, at least if GUI-programming is essential. My own prejudice has been that in future almost any major application will ideally involve more than one language:- -- an (OOP ?) language for its interface (say built using Eclipse, java) -- a procedural language for its novel procedures/plugins (say, FB, C, C++). Such plugins could hopefully be tested during development using an ad hoc front end not involving the big Eclipse-java apparatus. > Apple will support Java and its bridge to Cocoa Cocoa to java? Java to Cocoa? > (I also suggested to use Eclipse as a IDE-fundament for > FB, but this was never deeply discussed and today it > isn't worth while to think about it.) What about using (procedural) FBtoC to get compiled C plugins (and C sources) for Eclipse-Java-Cocoa-plugin frameworks ? > BTW, speed is definitely no longer a problem > with Java! Maybe just because java calls on some fast binaries compiled with solid procedural languages like C ? Or can someone point out convincing java versus C benchmarks --- revealing sources, binaries, and relevant dependencies? The above possibilities would really set me alite if they would facilitate some interplatform program devellopment involving FBtoC. They need not compromise FB's autonomy. Cheers Laurent S. PS. Question for Herbie or anyone else involved:- Is drag-and-drop of folders onto application icons still solid under current FBtoC ?