As a bonus, this one looks amazing (saw one in person this summer): http://spyder.brp.com/
That car looks suspiciously like a motorcycle.
I agree though it certainly beats out the Type-1e in the looks department. I don't understand why new-tech people insist on making such horrendously ugly vehicles. If they actually made them look like traditional cars they may have a chance of catching on.
I get that the design helps them achieve 300mpg, but seriously, no one is going to drive a Type-1e on a highway. It looks like it'd crumple like tin foil.
I hope you never complain about someone butchering the English language, because you are basically saying that it's fine to ignore the rules as long as everyone else does the same.
On the contrary, I'm thinking more along the lines of 'if the standard to do x is using code y, but everyone is using code z to make it work in the browser, then maybe z should become part of the standard'.
And btw, people butchering the language is exactly how languages evolve. Otherwise we'd still be using words like thou and forsooth and such wonders as ginormous would never have come into being.
Really though, if over 95% of the web isn't "standard" then maybe they need to rethink what is and isn't standards-compliant.
I haven't read TFA, but I assume they're only going by what the W3C standards are, and anything outside of those parameters gets knocked. But really, there isn't a single browser that's 100% standards compliant, so it'd be a better judge to see how many sites work across all the major browsers instead of how many sites' code matches a standard not even the browsers fully support.
...leave out the version number altogether. Just slap a "NEW!!" sticker on the box and throw it out the door. Marketing execs have spent whole careers making people think new == better. The average consumer won't even think about the version when they know it's the newest one.
And if this is the big problem at the product managers table, then start working on the patch now because you just know this thing is going to ship before it's ready.
As a bonus, this one looks amazing (saw one in person this summer): http://spyder.brp.com/
That car looks suspiciously like a motorcycle.
I agree though it certainly beats out the Type-1e in the looks department. I don't understand why new-tech people insist on making such horrendously ugly vehicles. If they actually made them look like traditional cars they may have a chance of catching on.
I get that the design helps them achieve 300mpg, but seriously, no one is going to drive a Type-1e on a highway. It looks like it'd crumple like tin foil.
The thought of the goatse guy being the goatse kid just made it ten times more horrifying... I'm not sure whether to curse you or applaud you.
I hope you never complain about someone butchering the English language, because you are basically saying that it's fine to ignore the rules as long as everyone else does the same.
On the contrary, I'm thinking more along the lines of 'if the standard to do x is using code y, but everyone is using code z to make it work in the browser, then maybe z should become part of the standard'.
And btw, people butchering the language is exactly how languages evolve. Otherwise we'd still be using words like thou and forsooth and such wonders as ginormous would never have come into being.
Really though, if over 95% of the web isn't "standard" then maybe they need to rethink what is and isn't standards-compliant.
I haven't read TFA, but I assume they're only going by what the W3C standards are, and anything outside of those parameters gets knocked. But really, there isn't a single browser that's 100% standards compliant, so it'd be a better judge to see how many sites work across all the major browsers instead of how many sites' code matches a standard not even the browsers fully support.
...leave out the version number altogether. Just slap a "NEW!!" sticker on the box and throw it out the door. Marketing execs have spent whole careers making people think new == better. The average consumer won't even think about the version when they know it's the newest one.
And if this is the big problem at the product managers table, then start working on the patch now because you just know this thing is going to ship before it's ready.