State of this library

[heapwolf]

This library is getting neglected. As the original author, I'd like to work on it but I'm no longer interested in the overall goals of flatiron and what it has become.

I'd be willing to maintain this project if it was transfered back my account. Why don't I just fork it? As I said, flatiron.

[ravi]

Paolo, I always liked that Weld was a no-DSL logic-less template but sort of lost interest in it after it was subsumed by Flatiron since I found the framework complex and counter-intuitive (no insult to the authors, it's just the way my mind works). I switched to using TransparencyJS. I would be very curious to see in what direction you take a forked Plates. Dynamic binding would make it very attractive and a right-sized challenge (as some guy once wrote, MicroFrameworks are dead :-)) to Angular, Ember, etc (I do realise that may not be your intention).

[Southern]

@hij1nx I've already started a recode of this, if you'd like to continue working on it. I haven't had the time to keep up with it the past couple of weeks.

[indexzero]

@hij1nx I'm a big +1 on the rewrite @Southern has been working on. As the biggest consumer of plates, we've encountered the most issues (@3rdeden can vouch for that) and I think are in the best position to ensure stability of future releases.

As for your opinions on flatirion, you're entitled to them, but it seems like more of a power-grab than anything else.