We get a fair number of visits, I think. For a rarely-maintained, grassrootsy, non-commercial site. Not a lot. We had under 400 visits the last month, according to Google Analytics, though most visits last over 2 minutes, and at least half our visitors are repeat visitors.
I have to assume folks are making use of JazzRecord in some way, and that they’re visiting to refer to the documentation. I don’t see any other explanation. I’d really like to get to know the users, and find out if we can do anything to improve JazzRecord short-tern and long-term.
Long-term, for instance, I’d like to move our documentation into the source code repo and simply reference/style that nicer on the Web site. I’d also like to provide better docs and add a few more features, like the ability to add indexes in a model’s declaration. I’m still considering the implications of async support eventually, though I certainly don’t have time to support this idea at the moment. We’d still like to translate the docs into other languages, but we need volunteers.
Short-term, I’d like to add some new adapters to the codebase. I’d like to support any new runtimes that may have cropped up lately. Node.js and similar are definitely on the list. Does anyone use Jaxer still? Is there an environment you’d like to see supported? So long as SQLite or a compatible dialect of SQL is supported, and so long as a *synchronous* API of some kind exists, JazzRecord can be added with very little effort.
Please, take a moment and comment, here or on Twitter. Let us know how you use JR and what you’d like to see in the future.