4 ms·
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 re
by FlowerPower 15y ago
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 15y agoThe 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 15y ago> Why would anyone do that? Business model of proprietary software, return on investment on lock-in of customers.
- extension 15y agoAs 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 15y agoCare to enlighten me on examples of languages that got a decent head start as a reference implementation, and are wide-spread?
- extension 15y agoUmm, all of them? Can you name a mainstream language that didn't start with a reference implementation?