Isn't chord detection / polyphonic audio analysis really difficult?
And they do it instantly using an iPad, that's really impressive.
It kind of makes me mad that Google "neglects" audio on Android. The well known latency issues are the reason developers choose an iPad/iPhone over any Android device :(
Bootstrap has a similar grid, but it also has nice styles for everything else.
Bootstrap is not targeted at someone with design skills or someone with access to someone with design skills. It's for programmers like me who don't have artistic ability who are trying to launch minimum viable products that still need to look professional.
I had originally started by trying to customize templates from themeforest, so my sites would look professional except for the parts I had to customize. This isn't good enough.
Bootstrap enables me to build professional looking websites from the ground up (Admittedly, my sites probably look very similar to many other bootstrap sites, but hopefully, they'll work on theming next).
It's much more than just a grid. It has patterns for buttons, modals, pop-overs, hero-units, forms and such (including a small unobtrusive JavaScript library). If you need to rapidly prototype designs and layouts, use it. We use it as almost a living wire-frame. Where we can see interaction and UI/UX very close to the full-design spec with little effort from a designer.
The grid is only one of its features. I get the most utility out of Bootstrap's prebaked design features that I have to custom code every time I start new projects. From warning/error/success messages to popovers to simple form aesthetics.
When the most primitive iteration of my application already looks great during development when it's just a simple CRUD prototype, I no longer waste mental energy by being distracted by things not lining up, lacking padding, and generally being no-css-yet ugly off the bat.
Even the typography in the framework is damn good. I only add a few fonts (like pictos for symbols) and I'm off. By adding a data-grid, additional alert/button colors I got 80% of my work done. It's pretty amazing for me.
But I only work on internal apps. I can see needing to do some serious customization for any public website. But the foundation to build all that is there.
Nokia produced the best mobile phones back in the day, solid quality and fair price.
They just missed the smartphone trend and when they still could get back they refused to be mere "hardware-producers" and out of pride they didn't cooperate with Android.
So in no way Amazon and Nokia are comparable.
The only thing I don't like about the Kindle Fire is that (although Android is used) the Android-Market will not be useable
I'm actually glad the Fire won't have the Market on it. Presuming it does sell like hotcakes; the Fire (and any related Amazon devices) becomes incentive for Google to ensure that Android stays open. Forcing a fork (by closing the source) would shatter the Android developer community; bigger devs have to use more resources to stay compatible with both sides, smaller ones have to choose a side, and some would decide to leave altogether for a more stable platform. Even if Google "won" the fork, they can't afford to send developers away.
Flip side, there's the possibility that this is exactly the scenario Amazon is hoping for.
their double standard on real/fake names is a disgrace.
they ban people for using their internet handle that they have been using for the last 15 years and on the other hand celebrities like madonna or 50 cent are allowed to use their artist names
I think most of that syntax isn't so much "advanced" as simply not used in practice--it's too hard too read. Additionally, it uses basic operators which you should know (except maybe for "^" which is bitwise xor).
The best thing to do would be go through the basics of JavaScript and learn exactly how everything behaves. You should be able to answer questions like "is 24&&4 === true?" pretty easily.
If you have a bit of time on your hands, reading the standard will teach you all you need to know.
Of course, from a purely professional stand point, this is probably not the best use of your time (although knowing the language inside-out is important); using code like this in production code is a bad idea--it makes maintenance much more difficult.
I always thought "it just worked" and they analysed it afterwards, silly me :)