[combataircraft]

What the fuck is going to happen when I need to reuse my JavaScript code on a different platform e.g NodeJS, vert.x etc?

I'm sorry for negative comments but, what ruby and .net communities produce for JS is shit. It's even more harmful then IE6 for our future.

[sandrew]

A couple of months ago GitHub released a coding guideline for Javascript. It has the first point: "Use CoffeeScript".

Except of using Coffee instead of JS your comment has no sense.

[combataircraft]

Github is not a rich web app for me. See Google Spreadsheets to figure out what a client-side framework should be helpful for.

[inossidabile]

You just take it and use it. Joosy doesn't make to write you code in some special way (except CoffeeScript but it can be used with node.js).

What's for binding parts (pages, layouts), I doubt you will ever want to use browser parts in node. So this is not the case.

[combataircraft]

All the JavaScript and templating code should be reusable by other platforms with no effort. It's required for testing, optimization and being able to move from one technology to other easily. This is the challenge programmers should solve. There has been already dozens of very good client-side frameworks that let us create very cool UIs with no effort but none of them is still good enough since the core idea is bad.

[inossidabile]

While you have a point, you seem to miss the original problem of browser frameworks. Browsers work _differently_. This is not the problem of a framework. Moreover nothing can stop you from using node.js + DOM mock to test anything you want. Unfortunately most of these tests will stay useless. So it's not about a possibility to write them. It's about a sense.

And btw, we are going to implement node.js tests to use Travis very soon.

[alerticus]

Sorry, but what are you going to do with the DOM related or browser oriented code on your NodeJS? In fact, Joosy is framework for the browser apps, this hasn't been told?