I drew the palm tree because I've studied AI and that's a classic AI mistake.
If you go to Hawaii and ask students to draw a tree, almost all of them will draw a palm tree. Ask them to draw a bird and it looks like a parrot (instead of the robin you see typically in the "lower 48").
It's interesting that this seems to suffer from the same selection bias.
http://timesofindia.indiatimes.com/city/goa/Coconut-tree-los...
I had to draw an aircraft transport, I draw a reasonable one. What it was expecting, instead, was a plane, As most people just drew that.
http://lesswrong.com/lw/nk/typicality_and_asymmetrical_simil...
1: http://www.theverge.com/2016/3/24/11297050/tay-microsoft-cha...
What I really want in there is the computer-generated music and sample-level speech synthesis they have limited demos of in the WaveNet post:
https://deepmind.com/blog/wavenet-generative-model-raw-audio...
https://www.microsoft.com/cognitive-services/en-us/computer-...
Would be interesting to for example submit the same blurry image with text to both services and see which one has the best algorithm to extract text.
Microsofts won and got far more things right. here is the output of the ocr scans: http://pastebin.com/YuRinwN2
here is the sample I submitted: https://i.imgsafe.org/c3147b06a3.jpg
I've often wondered at what point an AI would be able to play the game in a convincing way. Looks like things are getting closer!
I'm trying to develop an app which would do this with things people "draw into the air" with their finger.
Weirder still, the grid of videos doesn't use the Bootstrap grid at all. The elements are set to display: inline-block and then their width (and height, which we'll get to) is adjusted every time the window resizes using JavaScript.
This is presumably to maintain square blocks, because that's the design they've opted for and grid systems do not give you much control over height of the grid cells.
But using JavaScript to try and ensure squareness of grid cells is totally unnecessary. You just need CSS, as I shall demonstrate:
http://codepen.io/amdouglas/pen/eBddBd
http://codepen.io/amdouglas/full/eBddBd
Sometimes JavaScript is the best tool, especially in terms of accessibility; in this case, it adds nothing, only an expensive event handler. The resize event is really an awful way of achieving responsive web design. Media queries are the best option in 99% of cases.
* * *
Returning to the original thought, Google seems to have very different teams working here and there on their various marketing websites.
If you look at gv.com, their site also uses jQuery (with Slick and Velocity plugins).
If you look at duo.google.com and allo.google.com, they're Angular sites — which is what you'd expect from Google. A lot of their websites are based on Angular, it's a framework they're invested in (along with Polymer) and so on.
More recently, some of their marketing sites are being made with MDL. Usually small, less significant ones, not for apps but for random initiatives and projects that few people are going to look at. Which seems rather telling.
Polymer is in use, but seems to be reserved for applications like Youtube Gaming or Play Music. I think the Google PDF Reader is Polymer-based was well. That makes sense, Polymer is barely supported in browsers other than Chrome without a hefty bunch of polyfills.
There's also the Closure JavaScript libraries/tools, which Google used to use a lot for things like GMail (blog.google is the most recent instance I think).
For some reason, I find it odd that they don't have a unified internal toolkit for this sort of work. I'm not actually critical of this fact, I'm no critic of pragmatism. I'm just surprised.
I wonder though: does this indicate that these sites were outsourced to an agency?
