Editor when working with Nu + Cocoa / iOS API

124 views
Skip to first unread message

Andy Park

unread,
Jan 15, 2013, 7:58:37 PM1/15/13
to program...@googlegroups.com
Hi,

This is my first post after some time lurking :D

I've been programming for the Mac / iOS API's for a while now, and am looking into switching the language component in my tool stack. I love Ruby and over the last few years have spent a fair bit of time with MacRuby.

I can see from the conversation here that a few of you would be spending quite some time writing Nu code and using the Cocoa or iOS APIs. I'm curious how you deal with the famous verbosity of the API's. I hope I'm not going to start a religious war here, but I never really appreciated the high propensity for typos with Apple APIs, even when Obj-C was my bread and butter, and am annoyed with the trend of the method names getting even more ridiculous with each new version of the OS. After a year of working with Ruby-style API's and its brevity, I feel a bit apprehensive of having to type out the Cocoa method names again.

Since a few years ago auto-completion in Xcode became fairly decent. I'm assuming this would be no use when writing Nu code however, so does one type all the method names out when you call them, fiddling with the cases, or keep copying and pasting them from the documentation? Do you find the drop in efficiently authoring code is still made up by the productivity gains of lisp-y code? I'd be most grateful as a newbie if the more experienced can share a bit of detail about their code authoring environment and general workflow using Nu.

Johannes Goslar

unread,
Jan 17, 2013, 4:55:43 PM1/17/13
to program...@googlegroups.com
Hi Andy,
not having written much nu in the last months, but one way is to avoid cocoa in nu. :)
If I am creating your my dsl, it will have some calls to objective-c but only in "base" functions. The upper parts will be pure nu.
Anyway, you definitely would not have to give up auto-completion when parting from emacs. Emacs has some good auto-complete supports via different packages, it looks like it could be able to provide a great nu environment. There are even emacs-clang bridges.

Cheers
Johnny

--
You received this message because you are subscribed to the Google Groups "Programming Nu" group.
To view this discussion on the web visit https://groups.google.com/d/msg/programming-nu/-/Hk6kDiPn20oJ.
To post to this group, send email to program...@googlegroups.com.
To unsubscribe from this group, send email to programming-n...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/programming-nu?hl=en.

Reply all
Reply to author
Forward
0 new messages