News for hackers. Stuff that matters.

bear454

Re:Client-side JS MV* Framework Roundup on Wednesday March 27, 2013 @06:46PM (#5452466)
I'm tickled pink Angular is working for you.

I have to say, it looks really cool. But, its just not something we'd use in SUSE Studio.

I'm sure a thousand other people will have a thousand other ways of describing how I've slighted or misrepresented their project... and I totally expected that. It's a blog post, not a term paper - there's just no way to comprehensively describe everything about everthing.

That being said, the effort I put into making a responsible decision for my project wasn't one I took lightly. I'm sorry folks seem to think so, just because I tried (and slightly failed) to write a 3K word summary of 80 hours of JS framework madness.

Re:Client-side JS MV* Framework Roundup on Wednesday March 27, 2013 @06:39PM (#5452445)
Thx
Re:Client-side JS MV* Framework Roundup on Wednesday March 27, 2013 @06:25PM (#5452375)
> It appears that they did not actually try any other framework to be frank. Just noted their cons mostly.

Wrote code in every one of the 13 frameworks I mentioned. Thanks, though, for assuming I'm a complete jackass.

Re:Client-side JS MV* Framework Roundup on Wednesday March 27, 2013 @06:24PM (#5452368)
>> we would need to roll our own Mustache template compiler

> I'm not sure if I understand this point but why not just use Sprockets to compile templates? Or what do they mean by 'own [...] template compiler'?

We'll be using the same partials for both server-side and client-side rendering. Its enough we have to have two sets of controllers, and two sets of models; I'm not about to maintain two sets of views as well.