|
|
|
|
|
|
by mpweiher
4930 days ago
|
|
|
3) You think that having a common language for all parts of your project could be an advantage, for example sharing your model code. Especially valuable if you've decoupled your model from your delivery framework like Uncle Bob told you ...;-) http://www.confreaks.com/videos/759-rubymidwest2011-keynote-... 4) You find that the very small amount of spare time this sort of thing takes is worth it, even if just for kicks. 5) You miss WebObjects. 6) In addition to having code commonality, you might be interested in performance that allows you to not have to worry about scaling out for much much longer than other common solutions (or requiring rewrites if you're successful). For example, my own embedded Objective-C web lib (based on libmicrohttp) clocks in at around 30K requests/second even when initialized via script on my laptop, whereas something like Sinatra does around 900. http://blog.metaobject.com/2012/03/30k-requests-aka-wrk-is-f... http://blog.metaobject.com/2011/12/ruby-and-rails-scalabilit... 7) You think textual verbosity is a good thing when it adds to readability. 8) You want to embed a web-server in your iOS and/or MacOS X app. Peer to peer, like the Internet was originally intended. While it may be possible to achieve with RoR or Sinatra or the like, an ObjC lib is just less hassle. |
|
|
FTFY :)