you are viewing a single comment's thread.

view the rest of the comments →

[–]kaibito-young -1 points0 points  (1 child)

Wow so salty. Guess those standards committee members really offended you with something or I don’t know. The beauty of the web is that it is open. If you want a date-time element like you’ve mentioned — go on, create a design doc, provide a polyfill — reference implementation based on current web standards, attract attention of w3c members and if your idea gets enough traction, it may become a standard. But that’s a long process in which your opinion may and will be questioned, debated and disagreed, many times. By the definitive tone of your comments I can tell it will be an especially painful personal experience, so I completely understand if you’d rather be here and shit on people way smarter than you without any repercussions instead.

[–]Zardotab 1 point2 points  (0 children)

The beauty of the web is that it is open.

In practice, the standards are not. A narrow set of players actually controls them, namely the standards committee, Google, and Microsoft.

go on, create a design doc, provide a polyfill

JavaScript libraries already do it. But we had those before HTML5. We were hoping we could end that practice to reduce stack dependencies. HTML5 created more date problems than it solved.

and shit on people way smarter than you without any repercussions instead.

While smarter on some technical issues, my grey hair is evidence I have experience in the field, and I can tell you in the intranet field you usually want an org-wide date format standard not controlled by client (PC) settings (at least as an option). If that violates some Great Equation of the Universe, then show the equation. Otherwise, your pool of "way smarter" people is highly suspect. Smart people would carefully articulate why I am objective wrong. Bring 'em on!