3 ms·
Objective-J on the backend is still in it's infancy, so I'd recommend it if you enjoy being on the bleeding edge. We don't have any sort of Objective-J server-
by tlrobinson 17y ago
Objective-J on the backend is still in it's infancy, so I'd recommend it if you enjoy being on the bleeding edge.
We don't have any sort of Objective-J server-side framework, but you can use emerging JSGI-compatible JavaScript ones, like ActiveJS (Rails-like, http://activerecordjs.org/ http://activerecordjs.org/), NitroJS (http://www.nitrojs.org/ http://www.nitrojs.org/), Bogart (Sinatra-like http://github.com/nrstott/bogart/tree/master http://github.com/nrstott/bogart/tree/master) or just write raw JSGI application using Jack or custom middleware, which is actually perfectly adequate in many cases.
- boucher 17y agoWorth noting that 280 Slides runs the entire app on the server as well as the client.
- tlrobinson 17y agoYes I should also note that Objective-J and Cappuccino run well on the server-side (using the Narwhal standard library: http://narwhaljs.org http://narwhaljs.org), I only meant that there's no Objective-J server-side web application framework (which you don't need in many cases).
- cpr 17y agoCan you expand on what you mean by this? It could mean a lot of different things... Thanks.
- tolmasky 17y agoEssentially, we run the same code on the server side as we do on the client side in order to unarchive the objects that get archived on the client, and then operate on them. For example, when you hit "export", the presentation is archived, sent over the wire, unarchived (using the same exact model code), then converted to PPT or whatever. You could also for example make an entire UI in code on the server, complete with connections to abstract objects, then send that entire object graph over the wire and show it on the client.