| Not sure what you mean by lack of stable releases. Are you saying that the releases are not stable, or that the release schedule is not stable? Both -- the releases were generally infrequent and tended to have issues that require running the latest versions from git to resolve. We also do offer a clean installer. First, all of cappuccino works without installing anything. It's self contained in a single app folder. Second, the tools all come bundled in one installer, which puts files wherever you like, defaulting to /usr/local/share/objj. We ship the documentation with the same download. My experiences trying to build from source (which was necessary as the releases fell considerably behind the development with requisite bug fixes) resulted in a bit of a mess in my home directory and the destination root (as well as interdependencies between), rather than just building cleanly in-place, but perhaps I was operating it incorrectly. And as for the type-checking compiler part, we actually have an experimental type-checking runtime available on github. Improvements are, as always welcome. But not having a type-checking compiler is certainly par for the course in the JavaScript world, so I don't quite see how it counts against Cappuccino. The primary count against Cappuccino vs straight JS is the difficulty in tracking down issues when they inevitably emerge. It sounds like things might have improved for Safari 4 users, however. Not that I wouldn't mind type-checking for JS, too. All that being said, yes it is young, yes it is a moving target, and yes there's a lot of work left to be done. Absolutely. Please don't take my criticism as anything but friendly intent. |
We probably don't make that clear anywhere, sorry.