3 ms·
Or they've been spoiled by certain language features and it seems unbearable to go backwards.
by andybak 15y ago
Or they've been spoiled by certain language features and it seems unbearable to go backwards.
- 286c8cb04bda 15y agoWhat language features does Ruby have that Objective-C lacks? It's a bit more succinct, perhaps, but when you're calling out to Cocoa all the time, that succinctness is going to get thrown out the window.
- jballanc 15y agoRuby has "yield" which, while possible to replicate in Obj-C, it's not nearly as nice. Also, Ruby can yield arguments, and the block being yielded to is free to ignore those arguments. That's the sort of flexibility that can make Ruby so much more enjoyable to work with in high-level code.
- 286c8cb04bda 15y agoThat's a great example, thanks! I did some looking, and I found a few[1] examples[2] of coroutines in Objective-C, though none of them seemed fully fleshed-out. Even if they were, none were, as you say, nearly as nice as "yield". [1]: http://cocoadev.com/wiki/CSCoroutineTest http://cocoadev.com/wiki/CSCoroutineTest [2]: https://gist.github.com/1033477 https://gist.github.com/1033477
- deleted 15y ago[deleted]
- pjmlp 15y agoPersonally I find great that we have a native Ruby compiler, even if it means a static language with Ruby like syntax in the end. I hope for the day when we have better and more type safe languages for system programming. Most attempts so far, Modula-* family, Ada, Oberon and so on, failed to catch on, to my dismay. Still it does not hurt to know some C.