i think in cappuccino you do everything in the "backend". there's no need to write javascript/html/css ... which is good in a lot of ways (you can output source for different devices, and i'm even guessing you could generate different backends - php, .NET) - but i'm more interested in the js/AJAX everything model, lighter on the backend.
i've never worked in objectiveC/J but js seems nicer at first glance. but i may just be saying that so that i don't feel like i would miss something should we choose etxjs.
Actually it's the opposite, Cappuccino applications are mostly client-side, running on JavaScript. Objective-J is an extension to JavaScript, which gets compiled to JavaScript (either at runtime or ahead of time).
ok. ok. i misunderstood.
interesting. so why wouldn't i just write javascript? what is the value added? aside from the fact that i'm not coding in javascript (which i don't consider a negative)
JavaScript lacks several features useful in programming complex applications, namely classical inheritance, code importing, dynamic message dispatching. Objective-J adds these to JavaScript, but of course you still get all the features of JavaScript, since it's a superset of the language.
Any HTTP server. The runtime compilation takes place in the browser (the compiler is written in JavaScript). The pre-compilation uses a command line version of the compiler running in Rhino)
i think in cappuccino you do everything in the "backend". there's no need to write javascript/html/css ... which is good in a lot of ways (you can output source for different devices, and i'm even guessing you could generate different backends - php, .NET) - but i'm more interested in the js/AJAX everything model, lighter on the backend.
i've never worked in objectiveC/J but js seems nicer at first glance. but i may just be saying that so that i don't feel like i would miss something should we choose etxjs.
more feedback would be appreciated guys.