86 karma · joined August 1, 2009
A few minor things: While jumping to time points works, scrubbing does not. Instead, the notes image gets dragged. You could embed the image as a background-image instead of an <img> to prevent that. Or catch the dragstart event on it and return false (http://stackoverflow.com/questions/4211909/disable-dragging-...). A custom Rails error page or better error handling would also be nice (http://notezilla.io/bla). And there are a few console.log's left (TIME!!!! :)
Did you match the music to notes by hand?
"The size of the index of a search engine is estimated on the basis of a method that combines word frequencies obtained in a large offline text collection (corpus), and search counts returned by the engines. Each day 50 words are sent to all four search engines. The number of webpages found for these words are recorded; with their relative frequencies in the background corpus, multiple extrapolated estimations are made of the size of the engine's index, which are subsequently averaged. The 50 words have been selected evenly across logarithmic frequency intervals (see Zipf's Law). The background corpus contains more than 1 million webpages from DMOZ, and can be considered a representative sample of the World Wide Web."
Just last night I thought about this and went to sleep in despair :>
If someone scans my brain, builds an artificial copy, instantly cuts out my brain and inserts the new one, I clearly die (because I got my brain/me cut out) and my copy lives on. From the outside, I'm the same, but the first me died.
So instead, I get my neurons replaced with artificial ones, one at a time. If I drink a few beers, brain cells die but I'm still conscious. So gradually replacing my neurons one by one should be no problem; there clearly is no loss of continuity, I'm still me.
But what's the difference? Let's assume one neuron is replaced every second. No problem, nice and gradual. What if it's one every millisecond, every picosecond? Should make no difference, because it's still one by one. But, the faster you do it, the more it approaches "instant". And instantly replacing all my brain cells is the same as replacing my whole brain. Thus, I'm dead and my copy lives on...
Opa runs on the client and server and compiles to JS, so it got that advantage over Curl. But it's still a kitchen sink wrapper around existing technology, from a single vendor. Those seem to never work out that well.
It also formats the equations nicely and lets you copy them as PDF. Makes a decent formula editor for Pages (with simple formulas).
If the cursor is outside an area, the bigger and closer this area is the easier it is to purposefully hit. ⇔ If the cursor is inside an area, the bigger this area is and the farther away its borders are, the harder it is to accidentally leave.
Other languages yield interesting sounds too http://translate.google.com/#de|es|pvpvpvpvbvbvbvbvpvpvpvpva...
There's also a bug in Für Elise, it ignores the repeat signs.
Although the fill tool seems to have a very high tolerance. Fills the whole screen everytime. You could also add line smoothing for the drawing tools. There are reasonably fast algorithms you can use with bezierCurveTo (http://robsite.net/posts/smooth-path-in-canvas).
On the other hand they have the power to intercept and analyze the complete data- and phone communication without anonymization. They of course use it not only to find malware and security risks, as was intended in the bill, but to provide 'suspicious' data to the police and intelligence services (http://www.golem.de/0901/64639.html).
We also have data retention for all communication data for six months and have planned a nice censorship infrastructure to block domains (against child pornography for now), not unlike Australia or China.
But at least IE has only 40% market share... (http://www.browser-statistik.de/)