So, you are going to write a script that uses the GitHub API to walk the list of http://rubygems repos, and open an issue on each one, suggesting the use of Eefgilm, right?
Yeah, underscore was there but date wasn't. I guess my point was that there wasn't a date.js or some reasonable equivalent time library because date/time programming sucks.
I think that's the point, I think Angular is easier also. But once you've mastered Ember, what you can do with Ember in a timeframe, greatly exceeds that of Angular. It's extremely powerful.
My personal story is that while I liked Ember, it lacked a bunch of other things that were painful to find elsewhere and integrate with Ember (such as includes). I switched to AngularJS because it gives me all this (and many more) out of the box.
Still, I'm not going to start preaching that AngularJS "greatly exceeds Ember".
It's great to make the decision to focus on simplicity over scope - that's a good, defensible choice and I don't think anyone here will fault you for it. But an honest understanding of the extra features you gave up to make that choice will go a long way.
Huh, that's an interesting perspective. What makes it more powerful? Is it a higher level of abstraction thing, like PG suggests makes one language more powerful than another?
Small examples. Tried understanding something more complicates and got buried in lots of $ signs, scopes, directives, services. Sometimes stuff doesn't work as expected so digging through a huge swatches of angular.js code to understand how somethings works.
It sounds like UIKit Dynamics will make things like flicking tiles around a lot easier to implement, without creating a physics engine from scratch... And UIKit is generally more friendly to flat designs... And the whole game engine thing is built in now.
But the real value of the best games comes from game-play dynamics, and not just how well the app simulates physics. Hopefully these changes in iOS will allow game-builders to focus more on the things that really matter, rather than redoing the work every game needs to do.
Heh, good eye. Ultimately, I'm a pragmatist, and there isn't a blogging platform as flexible and as powerful as WordPress built in Rails. I like to think it is my pragmatic approach to learning Rails that separates my workshop from other ("Kitchen sink included!") training options.
It's true. With lots of my students, just getting running is a fairly large stumbling block. Everyone seems to hit a different issue. Hopefully some of the newer initiatives can resolve this. In the meantime, I'm trying to think of better ways to help my students. Let me know if you have any ideas!
