Hi there! I made this, it turn electro-luminescent materials (the make EL wire, EL panels/tape, EL paint) into a capacitive touch sensor
It is also an open source arduino compatible board based on the ATMEGA 32u4, so it is programmable using a micro USB cable, and can use it's port to output keyboard and mouse commands.
It can also be connected to wireless chips, like the NRF24, XBEE, or the ESP6822 wifi module to have installations or garments that are networked with each other.
Youtube promotes trending videos, so if you get a lot of views very quickly, particularly among a common demographic, then the video will be more heavily promoted, and is more likely to go viral.
Similarly, videos with lots of view tend to appear higher in search results.
I imagine that people at youtube are very aware of this, and put an effort into distinguishing ``real'' view (consistent demographic/trusted referer) and ``fake'' (spammy/ black hat SEO) views.
I don't think he will answer positively. It's only a demo and somehow I don't see him releasing an unfinished program. But I can imagine other people picking up his ideas.
Actually there is someone in the Vimeo comment thread who has started a live canvas editor(1) inspired by one of the demos.
great link! geez, this reminds me why i like to use web developer tools so much when i'm adjusting my CSS, HTML, and JS. honestly, a lot of my ideas come from real time editing. i love making small adjustments to my values and getting to see those take effect instantly.
First off, they mention that when the initial design decision was made, a similar operation cost ~$160, which is tenable for an operation that only happens once in a while. This is in fact a case of them getting bitten by the pricing structure changing after a reasonable design decision (at the time) was implemented.
Secondly, they mention that this is part of a larger issue:
"In our most common case we might have to add and delete
a couple items to the list property every once in a while. That would
still cost us well over $1,000 each time.
Most of the reasons for this type of data in our product is to
compensate for the fact that there isn't full text search yet. I know
they are beta testing full text, but I'm still worried that that also
might be too expensive per write."
This is a real problem that GAE needs to solve.
Finally, their problem doesn't seem to be that they need arbitrary precision, its that they seem to need fast location centric queries of a large database.
Geoboxes allow you to solve this problem correctly (and quickly), returning the results in the database that are closest to you. Matching on a geohash can end up serving the incorrect data unless you resort to hacks involving a number of queries.
1) You are making an assumption that the original design decision was made around cost. I bet the more likely fact is that they made the change and found out that it cost them $160. Remember, that was when AppEngine was a _beta_ product and it seems they got lucky the first time.
2) They seem to have an extreme use case. No one is going to argue that maybe AppEngine doesn't fit the bill for them. Or, one could argue that doing 6.5 billion writes times a large number of customers, across multiple datacenters is something that a lot of databases would choke on.
3) Running more queries, while admittedly hacky is less expensive than doing more writes.
