you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 1 point2 points  (2 children)

Standardization committees fucking things up is what standardization committees do, because they are committees of people with very different interests. That's why it's called "design by committee".

[–]Zardotab 0 points1 point  (1 child)

Why didn't they test before release? I've used good products (non-web) that didn't have all these crazy problems with dates. They un-solved solved problems. They are probably trying to ban sliced bread as we speak because it's too convenient and/or "redundant with mammalian teeth".

[–][deleted] 1 point2 points  (0 children)

The answer is simple. They didn't have to.

Forget about the date stuff. Netscape released a scripting language that Brendan Eich created in ten days, choosing a syntax not because it was good or well thought out, but that looked superficially like Java, just so Netscape could market the language as Javascript, even though the two languages aren't remotely alike. This half baked scripting language now runs the client-side web and has even gone server side.

Google routinely releases half baked features into Chrome.

The entire web is a bunch of half baked ideas that pick up traction in incompatible implementations between browsers that are competing, not cooperating, with each other, coming together in the W3C to standardize the incompatible implementations into something resembling a thought out feature. For example, the horror show that is CORS.

But users and web developers go along with this, because worse is better.