Could Ruby be Apple's language and API future?
parveenkaler.com
Could Ruby be Apple's language and API future?
1–10 of 80 posts
Re: Could Ruby be Apple's language and API future?
#2I dont see any concrete evidence that suggests Apples shift from Objective C in the linked article. Can you point to specific information that points to such a move. fyi pypy has a LLVM backend, as does haskell, I believe python is supported in Xcode too. Hence a similar article could have been written about Apple moving to python.
Re: Could Ruby be Apple's language and API future?
#3This would be all kinds of awesome, but I think it's probably a dream. To leap from ObjC to Ruby would be a absolutely massive undertaking for them.
That said, they've pulled off crazier shit before.
Re: Could Ruby be Apple's language and API future?
#4I dont see any concrete evidence that suggests Apples shift from Objective C in the linked article. Can you point to specific information that points to such a move. fyi pypy has a LLVM backend, as does haskell, I believe python is supported in Xcode too. Hence a similar article could have been written about Apple moving to python.
Apple is sponsoring the development of MacRuby. It's not sponsoring pypy or Haskell LLVM backends.
Re: Could Ruby be Apple's language and API future?
#5They just took a big hit in the nerd press for banning twenty years' progress in programming language design. I think they want an iOS development process painful enough that only committed specialists (who double as evangelists) can manage to ship, because everyone else would tend to write portable code that runs on competing platforms.
Re: Could Ruby be Apple's language and API future?
#6I've heard people suggest this before, but Apple doesn't seem to feel the same way. Ruby (even MacRuby) is banned on the iPhone along with every other language that isn't C or Javascript. Apple plays things close to the chest, but banning a language that you intend to base the whole platform around just doesn't make sense.
Syracusa isn't wrong that Objective-C is getting long in the tooth, but Apple has shown more interest in incrementally improving Objective-C than replacing it.
Re: Could Ruby be Apple's language and API future?
#7The world isn't ready for iPhone on Rails.
Re: Could Ruby be Apple's language and API future?
#8The world isn't ready for iPhone on Rails.
Yes, but isn't Rails one of the best ways to quickly deliver iPhone web apps?
Re: Could Ruby be Apple's language and API future?
#9This would be all kinds of awesome, but I think it's probably a dream. To leap from ObjC to Ruby would be a absolutely massive undertaking for them. That said, they've pulled off crazier shit before.
It's not really that crazy. Take a look at MacRuby — it's pretty close already. Apple just doesn't seem to have enough interest to replace Objective-C.
Re: Could Ruby be Apple's language and API future?
#10I've heard people suggest this before, but Apple doesn't seem to feel the same way. Ruby (even MacRuby) is banned on the iPhone along with every other language that isn't C or Javascript. Apple plays things close to the chest, but banning a language that you intend to base the whole platform around just doesn't make sense. Syracusa isn't wrong that Objective-C is getting long in the tooth, but Apple has shown more in…
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).