Hacker News Reader

Comment by catshirt | Hacker News Reader

cool thing is that it looks like the animation is pretty much generated from a json object (likely generated from the program). not that there's many other ways to do it, but still a nice simple implementation.

http://labs.adobe.com/technologies/edge/resources/ferriswhee...

View on HN

This and other tools like Hype seem to generate reams and reams of javascript (that file you linked is ~150kb of mostly repeats and slightly tweaked values). It seems a bit mad to me - is a large complex animation going to end up being a 1mb monolith of javascript?

Was it only in my browser the train was going faster on the inclines than on declines?

I thought the same. The animation does scale quite nicely though, which I found quite impressive.

I think this is because (as samwillis pointed out) the rollercoaster is actually going backwards, so the inclines are really the declines and vice versa. Why they are running the animation backwards is another question, though.

Technically, not JSON.

Why do you think it is not JSON?

It's just a regular JS object. JSON !== JavaScript object notation. E.g. according to the JSON spec, you should always quote property names (`{"foo":123}`) but regular JS doesn't require this (`{foo:123}`).

More: http://benalman.com/news/2010/03/theres-no-such-thing-as-a-j...

sure, but somewhat irrelevant, since the point is that the object can be (and likely is at some point) deserialized from json.

The rolercoster seems to be going backwards...

Reply on news.ycombinator.com