Something we are looking to change. The duplication is pretty annoying, but we use AssetGraph-Builder for our production build, which uses ngmin, which doesn't play nice with ui-router. Also, now that 1.3 errors globally when you forget annotations, using NgAnnotate is much more of a no-brainer.
We specifically looked at CanJS, Backbone and EmberJS. None of which have testability as a core feature. CanJS and Backbone barely mention how to do it, EmberJS has one tiny page on integration testing. Which practically means there isn't a established right way to do testing. And you as a developer need to figure it all out.
I personally think ember has the best testability story for both unit and integration testing. The screencast below shows how to get started with ember / QUnit and karma
Angular's dependency on the DOM for rendering will always make testing it very difficult. This will continue their move towards feature based testing. Feature tests have their use, but they do not scale and provide the least useful insight into why something is failing. They are also notoriously slow, so once you have a large test suite, it can easily take 20 minutes or more for feedback. I have worked with feature based test suites that take 2 hours to run. It wasn't fun.
What the hell is that part about kids and breakfast?! "Could be used to monitor and train kinds to use the right implements to eat breakfast". That is just messed up.
In all seriousness this is freaking awesome tech. Will definitely be huge, unless they fuck up the licensing or patent it to death.
> What the hell is that part about kids and breakfast?! "Could be used to monitor and train kinds to use the right implements to eat breakfast". That is just messed up.
Messed up? You're just looking at what it's doing, not how it can be applied. The ability to monitor a child with special needs with this sort of application is pretty amazing. Suddenly, this information can be transmitted and used to assist with therapy. Knowing how often a child uses a spoon/fork rather than his hands due to real data rather than parents recalling is powerful.
It also provides powerful feedback. A system setup to remind them child if they stop using their fork/spoon by showing a picture to remind them. This is already used in training. Unfortunately, it can't be automated. Tools like this would allow for that, and the potential is staggering. We are clearly years away, but this has the great potential to really help people.
That is a really great point!
I was really only appalled by the specific application of audio feedback used in the demo. And as such I blatantly discarded the whole idea of feedback systems. But when I think about it, that area is huge.
I really want one of those sensor plates with an arduino interface!
> And as such I blatantly discarded the whole idea of feedback systems.
That happens far too often. You have to disconnect yourself from only looking at one element though. Generally, you have an interaction taking place in the form of Event > Action. Something occurs, and then something happens. In this case, the method of eating is the event. The sound happens to be the action. However, you can always replace the Action with anything else (you can also replace the event with anything else.
Basically, this is how you should approach demos. Not as the end, but as the possibilities.
Man, been wondering the same thing! However, I believe these sites employ some kind of like-hijack as you reach the page. I kind of clicked on one of them. Or not even that, I saw some friend liking this crap, it said the website in the post so I copy-pasted it in the address bar. Saw crap. Left. Safe-checked my profile. Nothing. But like 15 mins later I checked my profile again, bam, there it was. I had liked this friggin crap by directly visiting this site!
Now I can't remember which one as I camped out on the newsfeed and marked all that crap as spam..
