>> And given that Apple doesn't hesitate to squelch tech when it feels like it, >> I'm clear that committing to any technology it hasn't blessed is "at your >> own risk."
While this is partly true, I don't see what Apple could realistically do to hurt MacRuby developers (and why they would do that). Actually, the fact that MacRuby doesn't ship as a public framework in Lion is a blessing in disguise since developers don't have to wait for Apple's blessing to use the latest version of the framework. So, the only valid argument I personally agree with is the current lack of iOS support, but even that, writing OS X and iOS apps is quite different and I don't think many people only use one code base for both platforms. - Matt On Mon, Oct 17, 2011 at 2:14 PM, Bryan Harrison <br...@bryanharrison.com> wrote: > Those are all interesting and useful points and I appreciate everyone's > willing to respond at length. As always, I wonder why extraordinary > generosity isn't part of the geek stereotype. > > Since I'm interested in developing for both OS X and iOS, "no Ruby on iOS" is > the clincher. And given that Apple doesn't hesitate to squelch tech when it > feels like it, I'm clear that committing to any technology it hasn't blessed > is "at your own risk." > > Still, MacRuby is very promising. I'll keep an eye out. > > Thanks again, > Bryan > _______________________________________________ > MacRuby-devel mailing list > MacRuby-devel@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
