Actually I can't see what you think MS is doing wrong by choosing a name people will remember. I'm not very fond of MS marketing at times, but at least choosing a well remembered name is something I can't see as anything but fair market practice for a change. I'd do that too if I worked in marketing, for a Linux distribution as well as for Windows. It'd be my job.
Since this is a pretty "open-source'y" site you're posting on, I think I should point out that your scheme will give every person compiling their own kernel/application/etc a different version number.
Yet, if they were ever so kind as to not change the formats, several businesses would be shut down.
You'd better not invest in those businesses, since changing the file formats is exactly what they didn't do between Office 97 and Office 2000 (except in Access to add Unicode support). See this document for more details.
Slashdot Mirror
Actually I can't see what you think MS is doing wrong by choosing a name people will remember. I'm not very fond of MS marketing at times, but at least choosing a well remembered name is something I can't see as anything but fair market practice for a change.
I'd do that too if I worked in marketing, for a Linux distribution as well as for Windows. It'd be my job.
_A_ certain company? Just one? Geez, you've been lucky!
No, I think that's rather Perl 19100 in the cases I've seen it happen :)
(That darn unix struct tm really needs fixing!)
Yes, ISO 8601.
Anyone volunteer for tech-support on that? :-)
You'd better not invest in those businesses, since changing the file formats is exactly what they didn't do between Office 97 and Office 2000 (except in Access to add Unicode support). See this document for more details.
Did this optimization even go into the FreeBSD source tree? (It's not in my system anyway, just checked)
(Haven't tested it myself though, I just got used to where my keys are :-)