3 ms·
Two notes of interest from the 300 new features list: http://www.apple.com/macosx/features/300.html http://www.apple.com/macosx/features/300.html "Ruby on Rai
by ralphb 19y ago
Two notes of interest from the 300 new features list:
http://www.apple.com/macosx/features/300.html http://www.apple.com/macosx/features/300.html
"Ruby on Rails: Work in a developer's dreamland. Leopard is the perfect platform for Ruby on Rails development, with Rails, Mongrel, and Capistrano built in."
Yeah, ok. But then there's this:
"Cocoa Bridges: Use Ruby and Python as first-class languages for building Cocoa applications, thanks to Objective-C bridges as well as full Xcode and Interface Builder support."
Now that is pretty friggin cool, and there might be a significant competitive edge there for the Ruby lovers/Objective-C haters.
I worked a bit with RubyCocoa (the open source project that is the basis for Apple's implementation) two summers ago, and it didn't quite seem ready for prime time then. But with Apple throwing its weight behind it, I'm suddenly pretty exited about writing Cocoa applications.
Edit: spelling.
- jamesbritt 19y ago> with Rails, Mongrel, and Capistrano built in. This is nice and all, but how hard is running "gem install" ?
- alaskamiller 19y agoRails was included with Tiger, but you had to do some funky things to update it and use it properly. This is just their way of saying you no longer have to do that.
- veritas 19y agoOr downloading Locomotive....
- inklesspen 19y agoYou ought to check out Nu: http://programming.nu/about http://programming.nu/about Inspired by Ruby and Lisp (uses sexps for notation), written in Objective-C so it has great interaction with Cocoa apps and frameworks. Check out an example: http://blog.neontology.com/posts/2007/08/19/a-glimpse-of-nu http://blog.neontology.com/posts/2007/08/19/a-glimpse-of-nu
- akkartik 19y agoNu is what I call a language remix. Combine the syntax from one language with the runtime of another. It's relatively easy to do; we should be doing more of these. Backward compatibility be damned. --- The ruby/smalltalk connection is a bit of a red herring; the 'inspiration' from them seems to be just inserting symbols in the argument list. Perfectly doable in lisp, just not very conventional. http://akkartik.name/lisp.html#bind http://akkartik.name/lisp.html#bind
- tx 19y agoIsn't that a violation of GPL? If you include GPL-licensed code into your product (and they claim that Ruby is built-in) you are supposed to have your entire source code available. Ruby interpreter is GPL, how come they can bundle it with proprietary OS?