3 ms·

While it's refreshing to see people talk about the things they did wrong and how they intelligently approached fixing them, building your own javascript framewo

• Bahamut 12y ago
  If I had to guess, none of the solutions back then sufficed for them. Batman has been around for a while.
  • funion 12y ago
    You're dead on. We started work on Batman some time ago now - options then were quite limited.
    • tericho 12y ago
      2 years ago I was exploring frameworks for an enterprise project. I tried Batman along with most others, I can easily see why building your own framework would have been an option any earlier than that. Most frameworks weren't even at 1.0 stable yet. I initially wrote a fairly extensive prototype with Ember, but there were breaking changes so frequently I couldn't keep up with the learning curve. In the end I chose Angular because it had the best documentation, Google dogfooding, and testing was an obvious priority. Worked out so well we're on our 4th major Angular app now.
  • adrianhoward 12y ago
    Yeah. I've made that kind of decision a few times in the past — do we use NewFramework or do we develop our own. It's a really tough call. I've been wrong (and right ;-) multiple times going down either path. The last time I had to make that sort of choice we went the set-based design / real options path and developed both in parallel for as long as we could. More expensive, but lower risk. I'm glad we did coz the decision we made four months in on which one to drop wasn't the one we would have made at the start.