The reference you give isn't for computer vision by the way. The ImageNet project isn't for image recognition. It's for a curated database of images which researchers can use to train algorithms or do other image based research. The error rate shown in the graph on that story (which you submitted) does not show computer vision image recognition error rate and %. It shows the number of errors in their own database which is human curated. In other words, right now if they have 1,000,000 images of cheesecake, and someone searches for cheesecake, and looks at the top 5 results they get, ~96.5% of the time the image will actually be cheesecake.
Having worked on a rather large, and well funded, computer vision project for one of the largest companies in the valley, I can safely say a few things. First, ImageNet database is very good and useful for image research. If you are going to be training an algorithm and need millions of well curate images, they are one nice place to go. Second, we are no where near approaching a 0% error margin on computer vision. Third, AI is certainly a thing and should be watched. It's neat and computer vision is one very neat and highly useful aspect of it. But please do not for a second believe that in 2016 a computer will be able to look at any random image of anything and actually know what it is.
"The web is the greatest entrepreneurial platform ever invented. Lowest barriers of entry, greatest human reach ever. I love the web. Permission-less, grand reach, diversity of implementation. Don’t believe this imaginary wall of access of money. It isn’t there." -DHH
There won't be any further separate io.js releases (except for critical security fixes). All of the features in io.js are available in Node.js v4 and above."
Haven't tried it. I don't think I would as its a SASS project and I prefer LESS. My initial thought just upon glancing the readme was that it seems a bit bloated. Starts out with some great options then it looks like they've defined variables for every system don't imaginable. I like typebase because it's a very complete base that you can customize and build on without having to tear apart. Typographic seems more framework-y which is a turnoff for me.
But that's just a first impression and my needs and preferences aren't everyone else's.
As an introduction to signals, The Scientist and Engineer's Guide to Digital Signal Processing is pretty good(http://dspguide.com/)
you should also read this woman's blog http://www.windytan.com/
