My recent article triggered a massive response on twitter and in the Web Authors' community, and that's exactly what I think was needed. Let me clarify a few things:
- Some say it won't be enough. That's entirely possible. Read it again: that's entirely possible. But at least I tried. And I did it because someone had to do it. I am accepting the fact some browser vendors could call me a painful asshole if it could help the Open Web. I'm not here to secure the market share of browser vendors. But I do care for the Architecture of the Web, its maintainability over time and even more for its coherence. I find non-WebKit-based browsers adopting -webkit-* properties a nightmare, and I will fight that as much as I can. Only then, if everything else fails, I'll accept to consider the last resort and terrible solution proposed by Microsoft, Mozilla and Opera.
- I think Microsoft, Mozilla and Opera have, like Microsoft did in the past, underestimated the negative PR impact or decided to live with it. That's where you can help. Show them they can't live with it. Force them to find another solution.
- Yes, I know that browser vendors have tried evangelizing web sites. Well... Opera has a large evangelization team dedicated to mobile. Mozilla has only a little one and not sure it's dedicated to mobile in any way. I have no idea for MS but they certainly have one. Now, all that evangelization happened far from public's eye. My goal with my article was to put it back under public scrutiny and request public's help to reach a stronger impact. That's why I wrote that your voice does matter. And it really does.
- Some say it's because of W3C's Process that slows things down. No it's not. When a browser vendor has Intellectual Property Rights on a feature, when that browser vendor does not submit a technical proposal for that feature to W3C and when that feature hits the whole Web, there's nothing the W3C - or even other browser vendors - can do without facing legal action on one hand, potential incompatibilities with the protected feature on the other. Blame that browser vendor, not W3C or its Process.
- Some say forget about the problem and use frameworks on the server-side. Oh come on. That's curing a severe wound with a plaster and Tylenol... And that's not always possible.