donut

There is already such a game, kind of:

http://www.ea.com/auditorium-iphone

Some of the levels are pretty hard!

This reminds me of run-sequence and lag plots:

http://www.itl.nist.gov/div898/handbook/eda/section3/runseqp...

http://www.itl.nist.gov/div898/handbook/eda/section3/lagplot...

The field of Exploratory Data Analysis (EDA) is full of great techniques. See the root of the above guide.

The syntax looks very similar to JSONML, which has its own templating thing JSONML BST:

http://jsonml.org/ (http://webcache.googleusercontent.com/search?q=cache:http://...)

http://jsonml.org/bst/ (http://webcache.googleusercontent.com/search?q=cache:http://...)

Sounds like "The Free Music Philosophy": http://ram.org/ramblings/philosophy/fmp.html

Nice. Looks similar to http://jsfiddle.net/

Good read, thanks for that. I agree with the conclusion: there is no one-size-fits-all rule for interoperability.

The way I see it, it's ultimately about tradeoffs. I can only imagine what things would be like today if web browsers implemented a strict parsing of HTML and refused to render invalid pages. One possibility is hindered adoption of HTML by the masses. Another is that two vendors would disagree about the HTML spec and cause pages to be browser-specific. (Turns out this happened anyway :-))

Is the HTML5 spec better in terms of interop and compatibility than the previous ones? http://www.tbray.org/ongoing/When/201x/2010/02/15/HTML5

It has crossed TBL's mind:

"I have to say that now I regret that the syntax is so clumsy. I would like http://www.example.com/foo/bar/baz to be just written http:com/example/foo/bar/baz where the client would figure out that www.example.com existed and was the server to contact. But it is too late now."

http://www.w3.org/People/Berners-Lee/FAQ.html#etc

"Be liberal in what you accept, and conservative in what you send." - http://en.wikipedia.org/wiki/Robustness_principle

Nice writeup. After reading the first paragraph, I challenged myself to come up with something and here it is:

https://gist.github.com/a982f1fee5116d289323

Example run:

  expected:
  a 0.166666666667
  b 0.333333333333
  c 0.5
  
  observed:
  a 0.168
  b 0.291
  c 0.541

For a list of n items to choose from, it appears that pick() will terminate on the first iteration of the scary-looking while 1 loop with probability ~1/n. For n = 3, and I've run this many times, I've not seen the number of iterations exceed 30. For n = 26 it easily goes into the ~200 range at the extreme.

Regardless of the syntax for encoding a server event, having a request id (txnId in the post) is an often overlooked detail. See how Google do this in their systems: http://highscalability.com/blog/2010/4/27/paper-dapper-googl...

I'll probably get dinged for making a sophomoric observation.

Their example code makes use of the variable $hit, performs a var_dump($hit) and then returns $hit. Am I the only one that noticed this?

Frequent physical component failures mean cloud/furnace engineers would have to knock on people's doors all the time.

"Hi, I'm from the Internet. Your furnace is beeping? Yeah, I've got a spare uhm.. heating element."

> Nikon S95

Doesn't exist, AFAICT. Do you mean Canon S95? If so, the Canon S95 is excellent.

Dude, I'm gonna have to decipher that one too??

I've updated the code to be even more readable, and as an aside, made it more optimal.

sin(A) and sin(B) were being computed repeatedly in the most inner of inner loops, which I pulled out, because A and B don't change in the middle. sin(j) and cos(j) was being computed for every i, even though j wasn't changing. And the intensity was being computed even if the pixel was going to appear beyond the buffer (or wasn't going to appear at all because of a closer pixel in the z buffer).

I also refactored parts of it, and gave names to some constants which you can tweak for fun. DELTA_I can be increased without apparent detriment to image quality. I can't think of good names for the two constants in the middle of the code though: 2 and 5. Are those the minor and major radius of the donut?

Here's a more readable version:

https://gist.github.com/1073922