- I'm investigating Incrementally Migrating to React-Native.
Mar'2015: Dan Yoder says: There's been a lot of excitement lately about React. React seems to have bumped Angular JS from the top of the hippest-framework mountain. This is unfortunate, because both of these frameworks are bad for your application's health. They're also bad for the entire software industry. For new applications, please, for the love of all things open, use Web Components instead... So why release an open source Web framework at all? Because Facebook is battling Google for engineers. So you've got a big fight between two companies over which company is the coolest place to work... both Google and Facebook are desperate to find a baseball cap that they can put on backwards. Angular is Google's baseball cap. React is Facebook's.
- Jun'2013: I've written a new ebook. It provides a detailed introduction to Ember.js.
- Jul'2013: I bought his book, but haven't started yet, as I don't have anything to build with it at the moment. But expect that will change in a couple months...
- Jul'2013: I wrote better software with Ember than I did with Backbone, and it's taken me a long time to get comfortable with that -- even after writing my Ember book -- but I've figured out why. I didn't want to admit to this fact because I didn't want it to be true. Backbone prioritizes simplicity and transparency, while Ember holds your hand through a lot of the scary parts of building an app... And speaking of "fighting the last war," I haven't yet seriously investigated Angular, Knockout, or any of the several other alternatives. There's always something new.
- Sept'2013: the Ember App Kit
Edited: | Tweet this!