in my django stack, i already have shpaml+sass+templating. this by itself, already fulfills all my html+css needs, and it makes it retardedly easy to work with. why would i need to change something that is already working?
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... !
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
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.
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... !