First off - I liked the game. It was fun. No arguments there. But (and nothing against the author of the game)... I'm going to jump on the bandwagon here of o

First off - I liked the game. It was fun. No arguments there. But (and nothing against the author of the game)... I'm going to jump on the bandwagon here of others wondering just what the person or committee who thought up the API was smoking when they came up with it? At first, it made kinda sense. Nothing too troubling. But the deeper it went, the less it made sense. I don't have a problem with 1 vs 0 indexing (because I started coding in old-school BASIC back in the dinosaur days of microcomputing - so that doesn't bother me much). It's just that the rest of the API seems arbitrary, or random, or maybe ad-hoc. Like there were 10 developers working on the task of implementing this, but with no overall design document to guide them on how the thing worked. I'm really not sure why there's two (or three? or four?) different ways to express the same idea of a "span" of row or column cells, based on left or right indexing, or a span argument, or...??? Seriously - the whole thing feels so arbitrary, so inconsistent. This API has to be among the worst we have seen in the CSS world (not sure - I am not a CSS expert by any means). I can easily see this API leading to mistakes in the future by developers and designers. We'll also probably see a bazillion different shims, libraries, pre-compilers, template systems, whatever - all working on the same goal of trying to fix or normalize it in some manner to make it consistent. Unfortunately, all of these will be at odds with one another. I'm sure JQuery will have something to fix it (if not already). Bootstrap too. The dumb thing is that had this been designed in a more sane fashion, such hacks wouldn't be needed.