separate frontend/backend code about cobalt-calibur-3 HOT 2 CLOSED

Hi,

There isn't any interest in rewriting the backend in clojure. If clojure
supports websockets and the same fallbacks that socket.io supports, it
might be possible to fork the project and completely rewrite the backend
and use the same frontend.

Everyone who knows coffeescript also knows javascript, but not vice versa,
so to write it in coffeescript would limit the number of developers who
would benefit.

On Thu, Aug 16, 2012 at 3:33 PM, Joel McCracken [email protected]:

Awesome project! I was looking for something just like this. Only a few
problems:

I'm not very interested in Node. If I were to play/contribute, would
almost certainly implement a clojure backend... which brings up the idea,
do you have any plans for this?

Additionally, is there any clear reason to not have used coffeescript? I
much prefer coffeescript, personally.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/25.

Thomas Hunter
@tlhunter http://twitter.com/tlhunter
thomashunter.name

from cobalt-calibur-3.

Hello,

I may do that. Ideally, it would be nice to have separate components, so as to maintain some sort of interoperability. Maybe not, though. I will keep this in mind.

I'll close this issue, as I dont have time to play with this right now anyway. Feel free to ping me if modularizing the code sounds useful at all.

from cobalt-calibur-3.