[veosotano]

So can you do "myElement { alignY: 50% }" or something like that to automatically center vertically in your browser?

Or can you do "100% - ref(width of sideColumns)" to create two fixed-width and one fluid column in the middle?

Or can you rely on having exactly the same interpretation of your code across all browsers?

...

I guess you are looking at just a limited subset of what AXR is, mainly the syntax features that are similar to SASS and the like, while ignoring all the other problems it solves.

Of course we can do websites now, but no one says it's easy. Just think at all the productivity gains and improved user experience... !

[FlowerPower]

Why do you think AXR would have the same interpretation across all browsers? Dont you think somone cough will make their own implementation that fucks up the rendering/layouting just for the heck of it? cough

[veosotano]

The reason is because that's one of the main pieces of the project. Providing a library that browsers can USE, not IMPLEMENT.

Why would anyone do that? That's WAY too much work just for fucking something up just for the heck of it.

[FlowerPower]

> Why would anyone do that?

Business model of proprietary software, return on investment on lock-in of customers.

[extension]

As long as the reference implementation gets a decent head start, any re-implementers will practically be forced to maintain complete compatibility with it. This model works quite well for programming languages.

[FlowerPower]

Care to enlighten me on examples of languages that got a decent head start as a reference implementation, and are wide-spread?

[extension]

Umm, all of them? Can you name a mainstream language that didn't start with a reference implementation?