Ruby is an impractical language so, no.
Could Ruby be Apple's language and API future?
21–30 of 80 posts
Re: Could Ruby be Apple's language and API future?
#22Earlier quoted context omitted.
They could change 3.3.1, but they didn't have to blanket-ban Ruby to begin with — they made already have four languages they allow. The fact that Ruby was banned shows that they don't even place it on a level with C++, much less Objective-C. On top of that, MacRuby was just starting efforts to target the iPhone when Apple banned it, leading the developers to throw their hands in the air and say, "Oh well, didn't real…
Just remember that we're talking about a company that managed to migrate its entire product line to an entirely new processor with few people (inside and outside the company) really knowing until they unveiled the first demo machines. Compared to that, adding a new programming language (that doesn't even affect their existing 3rd party applications) to a platform they own completely is child's play.
I think we're talking past each other. All of your comments seem to be arguing that Apple could do this if it wanted to, while all of my posts are arguing that Apple hasn't shown any desire to do this.
Re: Could Ruby be Apple's language and API future?
#23Re: Could Ruby be Apple's language and API future?
#24Re: Could Ruby be Apple's language and API future?
#25I can't really see Apple doing this, if for no other reason than Objective-C is something they can control, and Ruby isn't. If the core Ruby developers decide they want to add more features, change the language's underpinnings, etc. Apple's left to play catch-up. If Apple wants to add features, then they basically have to fork the language and hope their changes get merged in. Apple's shown (and been shown) how much…
They control MacRuby, and indeed have added new syntax. MacRuby is actually not forwards compatible with regular ruby.
Re: Could Ruby be Apple's language and API future?
#26It would be cool if they will sponsor some effort to marry ruby and llvm. ^_^
Re: Could Ruby be Apple's language and API future?
#27It seems extremely unlikely that Ruby will displace ObjC. I can imagine that it will become the blessed scripting language for the Mac, in something like the way that Visual Basic has been for Windows.
Either way I'm glad to see Apple's support behind Ruby.
Re: Could Ruby be Apple's language and API future?
#28Earlier quoted context omitted.
Apple is fortunate that they're the only ones they have to check with to change 3.3.1. When the hardware has gotten ample and the software is mature enough, I for one won't be surprised if we see revisions. Meanwhile, a blanket ban will accomplish their goals just fine (take your choice: blocking Adobe, preventing fragmentation, making developers choose single platforms, etc).
They could change 3.3.1, but they didn't have to blanket-ban Ruby to begin with — they made already have four languages they allow. The fact that Ruby was banned shows that they don't even place it on a level with C++, much less Objective-C. On top of that, MacRuby was just starting efforts to target the iPhone when Apple banned it, leading the developers to throw their hands in the air and say, "Oh well, didn't real…
Yes, they did have to blanket-ban it to begin with. If they're to make an exception for this, then in the interest of avoiding fragmentation they won't be making an exception for the Ruby language in the abstract; rather they'll be making the exception for the MacRuby implementation in particular. MacRuby is a unique implementation, and programming Cocoa through MacRuby is vastly different (and incompatible) experience from programming Cocoa on other OS X Ruby implementations.
Given that MacRuby is not considered "stable" just yet, the time is not right for Apple to provide an exception to 3.3.1 for Ruby programming. If this does happen, then it will happen only after MacRuby is good and ready.
I emphasize that I do not support Apple's draconian policies toward iOS developers, but their behavior here is internally consistent with the possibility of an eventual allowance for MacRuby.
Re: Could Ruby be Apple's language and API future?
#29Unlike many of the other commentators, this seem feasible enough, given another year or so and some progress in terms of performance and the API.
I think it’d be great to have the option to write Mac apps in Ruby instead of in Obj-C, and it seems rather Apple-like to be the first to having a language like Ruby be a primary/supported system language. Wouldn’t mind seeing a Lisp there instead, but Ruby's a bit of the way there, at least!
Re: Could Ruby be Apple's language and API future?
#30Answer: No.
MacRuby is awesome, but it'll likely eventually suffer the same fate as the Java Bridge.