raorao

that's dependent on the problem at hand. Are you building a site that has a lot of moving parts on the same page, that needs to communicate nuanced state changes across components? If so, react/flux is a godsend, since the system will be easier to maintain and customize.

Is your site made up of many different views that don't change much once loaded? Then angular would be a fine tool for the problem. You would likely move much faster initially, since Angular handles a lot of problems with data binding and routing for you.

And finally, are you sure you need either of these frameworks? If you want your front end to consume JSON but it isn't particularly dynamic, something like backbone will probably be good enough. Hell, server-rendered templates do the job in a lot of cases. No reason to solve a problem that doesn't exist.

I agree with your general philosophy towards ICF.

hey everyone -- I'm actually one of the three developers-in-training who wrote this app. We just finished week four of Dev Bootcamp, and this was just a (admittedly stupid) project we invented to practice our abilities in html/css/javascript/sinatra/rspec/heroku. We built it in four hours late on thursday night, basically on a dare.

Also -- we love helping people! sitting down and walking someone through a problem is the best way to help them learn something and to crystalize the concept for yourself. Hell, thats basically the motto of DBC. And of course it's against the ethos of the programming community to belittle others who ask for help, since we're all going to need help at some point.

This site is just meant as a joke. I would hate it if someone actually used this on a curious and well meaning junior developer.