inossidabile

Active links (that for some reason did not activate at post itself):

README: https://github.com/inossidabile/protector

Intro: http://staal.io/blog/2013/06/04/the-protector/

We are waiting for 1.2.0 Vagrant release to make use of the librarian plugin. Vagrant self-installer will solve Windows issue. It contains several tiny bugs atm unfortunately :(

We moved it to http://rove.io

We were only able to add packages that we use ourselves for now. It will take some time but we are going to expand the list.

Makes sense. We will consider changing it. Thank you.

Well... That's just a name after all. Short and memorable.

The site itself (joosy.ws) is hosted on a company server. The repo is on github but it's private. However, Guides are in public repo (hosted at Github Pages).

Here they are: https://github.com/roundlake/joosy-guides

If you want to modify something at welcome page, I can share the repo. But it doesn't contain a lot actually. Just one page :).

What a dumb joke it would be %). Fixed, thank you.

Take Ember for example. Joosy is only 2-3kb more including Sugar. Compare the profit. One framework can not (and should never try to) address everything. Sugar beats Underscore without a hope (http://borisstaal.com/post/24270017179/please-use-sugar-js). And you just can't live without both, raw JS is too poor.

Fixed! Thanks for the catch! :)

Agreed. It's planned already in fact. Just need some more hours in a day :)

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.

If you don't, please take a moment to share your thoughts with me :)

It will work with any Rails JST binding. Just use .jst.slim instead of .jst.hamlc (remember to use JS version and not Ruby one :D). Everything that has a proper binding to Rails should work out of box.

For everything else, it has an abstraction layer so you can attach any template engine. We are woking on a guide that describes this process.

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.

Reusability is a thing that comes from your hands and not a framework. Of course, framework can influence it a bit. But we promote correct encapsulation at each layer. What exactly you think is wrong?