Only American and Swahili use mm/dd for dates
-
I'd like to response with another question. Imagine that you have international project with 20 countries involved, but 90% of your income is generated by USA customers. Which format you will choose? USA or Canadian? Another use case, imagine, that initially all your customers where from USA and only in two years after launching your product, you got those customers in other countries. What as usually customers ask: change format of dates or some other feature. From my experience issue with dates formatting was in backlog, but as usually it is not in high priority.
-
What's the point of either version? They both sort badly. I pretty much always use yyyy.mm.dd for all my laundry dating coding and business items. Only when forced due to specifications on a form (which always say what they want in each field and/or how they want it formatted) do I do otherwise. So - not to worry - Bigendian or little Endian - the egg breaks when you drop it from high enough.* * Not a relevant catch-phrase but something like that was needed.
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010
W∴ Balboos wrote:
What's the point of either version? They both sort badly.
The same can be said about e.g. (physical) mail addresses. They would sort much better if they started with the planet identification (or, if you want to go further out, the galaxy and solar system identification), then the continent, the country, the town, street, house number, floor, last name, first name. Same with DNS addresses - domains, email addresses etc. Before the current internet address structure squeezed out all its competitor, there were addresssing schemes listing elements from major to minor units. At the binary level, i.e. 32 bit IPv4 or 128 bit IPv6 addresses, the biggest unit comes first, but not in the DNS format. I guess the justification for putting the biggest unit at the end is that it makes it more natural to chop it off. You don't have to identify the galaxy when sending a postcard to your grandma. In most cases, even the country name is not required. If we had turned the order around, interpretation would in many cases be ambiguous: Is "Norway" a Eurpean country, or a US village? We write arabic numerals with the biggest unit to the left. So does the arabs, even though they read from right to left. The number is the same, but in the reading order, we see the highest digit first, they see the lowest digit first. Which is the most natural? In many German-related languages, numbers are pronounced smallest unit first, and you can see it in some old English as well: "... Four and twenty blackbirds baked in a pie ...", as the children's rhyme goes. Larger numbers are read in a mixed manner ("three hundred, four and twenty"). Natural language is a mess. But fun to study.
-
You forgot to mention miles per gallon. Not only does it use imperial measurements, it also deviates from the UK measure by the same name.
GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)
Stefan_Lang wrote:
You forgot to mention miles per gallon.
I was always fascinated by this approach, which I see as very 'American Style': I've got some resources (i.e. gallons of fuel) that I am going to exhaust - how much fun will it give me? The European approach is the other way around: I've got a task that must be performed: Driving 100 km. How much fuel is that going to cost me? ... not 100 km pr liter, but liter per 100 km. I do think that this says something about American philosophy as compared to European.
-
or, in American, the eleventh of September?
- I would love to change the world, but they won’t give me the source code.
-
Oh, and Micronesia. At least according to Wikipedia. So why does pretty much every US based service that caters to a worldwide audience use mm/dd/yyyy as a date format Latest example this hour is VS team services "Access issues with Visual Studio Team Services – 5/25 – Investigating". 5/25 = 25 May. That's easy. But when I see 6/7 or 10/8 I have to manually check the site and see what culture they are based in. No one in the US (I'm guessing - apart from ex-pats) worry about this. Or are probably even aware of this issue. Everyone else in every other country is aware of this issue. Everyone in Canada manages to deal with it. And I don't know how their brains don't explode. Canada uses dd/mm/yyyy. Except when it uses mm/dd/yyyy because either it's a US based company, they are using a US based system, they are trying to be nice to their US based customers, because they just forgot to use dd/mm/yyyy or because they know it's me and so they deliberately use an ambiguous date format to do my head in. Date formats in Canada are totally and completely messed up. So: Why, in this day and age, do those in the US, when writing for an international audience, still use mm/dd/yyyy? (And I'll add another one: Why do companies in the US find it impossible to ship outside the US? It's very odd) OK, back to hitting refresh several times a second waiting for Team Services to come back online.
cheers Chris Maunder
American way of date has its historic roots, but nobody forces 'em to pull such sht in IT! Moreover - why to use digits at all?! Even their idiotic date format can be human readable if it was "May/4/2016"! But they are too dumb and conservative to use progress. They invented computers... just to sell hotdogs faster! :)
-
W∴ Balboos wrote:
What's the point of either version? They both sort badly.
The same can be said about e.g. (physical) mail addresses. They would sort much better if they started with the planet identification (or, if you want to go further out, the galaxy and solar system identification), then the continent, the country, the town, street, house number, floor, last name, first name. Same with DNS addresses - domains, email addresses etc. Before the current internet address structure squeezed out all its competitor, there were addresssing schemes listing elements from major to minor units. At the binary level, i.e. 32 bit IPv4 or 128 bit IPv6 addresses, the biggest unit comes first, but not in the DNS format. I guess the justification for putting the biggest unit at the end is that it makes it more natural to chop it off. You don't have to identify the galaxy when sending a postcard to your grandma. In most cases, even the country name is not required. If we had turned the order around, interpretation would in many cases be ambiguous: Is "Norway" a Eurpean country, or a US village? We write arabic numerals with the biggest unit to the left. So does the arabs, even though they read from right to left. The number is the same, but in the reading order, we see the highest digit first, they see the lowest digit first. Which is the most natural? In many German-related languages, numbers are pronounced smallest unit first, and you can see it in some old English as well: "... Four and twenty blackbirds baked in a pie ...", as the children's rhyme goes. Larger numbers are read in a mixed manner ("three hundred, four and twenty"). Natural language is a mess. But fun to study.
You do know that computers don't give a damn about data format so long as they know how to interpret it. Why the DNS order is like it is? Truncation would make a good reason: it's as easy to truncate the front as the back (same, to, with masking, so far as that goes). If there's to be any controversy as to why either choice, I'd look at the every famous Motorola vs. Intel format for storage of numerical values: Big Endian vs. Little Endian. Both work - so long as you know what's coming. Now for the date formatting which I noted, above, one could argue that the US method is better if you leave off the year (not uncommon) for then it can be sorted naturally. The Euro-system is part of the same Obsessive-Compulsive disaster that brought on the metric system. I draw your attention to the following that you may realize the error of your ways: The Lounge - CodeProject[^] and even in my youth, oh so many years ago, The Lounge - CodeProject[^]
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010
-
Mike Mullikin wrote:
All we ever hear is how horrible we are. How we do everything wrong
Until a natural catastrophe occurs and then suddenly the US is there handing out food. Or when someone invades their country and they cry to US for military intervention. Or when their economy goes down the toilet and then reach the the US foreign aid. Or when.... ... you get the idea.
If it's not broken, fix it until it is
Kevin Marois wrote:
Until a natural catastrophe occurs and then suddenly the US is there handing out food.
The thing is, you have been doing that since the Marshall Plan: Establishing a market for American products, getting rid of surplus production. (Not only abroad - "The higher power of Lucy" children's book can give you some good laughs about the military surplus food!)
Or when someone invades their country and they cry to US for military intervention.
And sometimes they certainly do NOT cry for US intervention. Well, maybe a few unsuccessful politicians want to use the US Army as a tool to overthrow their competition, but maybe not even that. Iraq comes to mind.
Or when their economy goes down the toilet and then reach the the US foreign aid.
Like, when their economy was completely independent of the manipulation done by US investors - that's when it had its breakdown. At that time American capital came in and saved their economy, and proved the success by making enormous profits in the country. Great!
-
Bluddy French supporters! You are aware, I assume, that the reason that Europe began driving on the right is because the British (sensibly, and because they were the first to make such a decision) decided to drive on the left, aren't you? Mon Dieu! l'anglais les voitures d'entraînement sur la gauche! Nous devons conduire à droite! So Americans are just frog-leg lovers! Thought so. Me, I prefer my (strong) right hand to stay on the steering wheel, whilst I'm changing gear, etc.
I wanna be a eunuchs developer! Pass me a bread knife!
Forced into another obligatory reply: It's well know what you EU'ers are doing with your right and why you need it hand hidden by the door.
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010
-
Stefan_Lang wrote:
You forgot to mention miles per gallon.
I was always fascinated by this approach, which I see as very 'American Style': I've got some resources (i.e. gallons of fuel) that I am going to exhaust - how much fun will it give me? The European approach is the other way around: I've got a task that must be performed: Driving 100 km. How much fuel is that going to cost me? ... not 100 km pr liter, but liter per 100 km. I do think that this says something about American philosophy as compared to European.
It might be related to the fact that fuel is so much cheaper in the US than in europe. Here in europe, when you buy a car, you estimate the cost of the fuel it needs because it is a significant part of the full cost of owning a car. In the US, the fuel cost is comparatively insignificant compared to the price of the car itself. With that in mind, l/100km is a number that much is easier to gauge and compare: 20% more fuel consumption means 20% more fuel cost. Easy. Example: You can set back 100€ per month to be able to buy a new 12000€ car every 10 years, but if you are driving 20000km per year, and the car needs 10l/100km, that costs another ~3000€ per year, or 250€ per month! (350€/month total) So it might make more sense to set back 150€ per year for a 18000€ car that only needs 6l/100km, or 150€ per month (300€/month total). In the US, fuel costs a fraction of what it costs here - the calculation above would never work out.
GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)
-
You do know that computers don't give a damn about data format so long as they know how to interpret it. Why the DNS order is like it is? Truncation would make a good reason: it's as easy to truncate the front as the back (same, to, with masking, so far as that goes). If there's to be any controversy as to why either choice, I'd look at the every famous Motorola vs. Intel format for storage of numerical values: Big Endian vs. Little Endian. Both work - so long as you know what's coming. Now for the date formatting which I noted, above, one could argue that the US method is better if you leave off the year (not uncommon) for then it can be sorted naturally. The Euro-system is part of the same Obsessive-Compulsive disaster that brought on the metric system. I draw your attention to the following that you may realize the error of your ways: The Lounge - CodeProject[^] and even in my youth, oh so many years ago, The Lounge - CodeProject[^]
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010
W∴ Balboos wrote:
You do know that computers don't give a damn about data format so long as they know how to interpret it.
In that sense, there is no difference between humans and computers. If you give a computer the date 9/11/2001 and tell it "Interpret this as a date in American format", or you do the same to a human, it comes out right. If you tell the computer the date 9/11/2001 and tell it "Interpret tis as a date in European format", you get a different result from the computer, and so you would from a human given the same instruction. What regards DNS names: No, they cannot be truncated. You have to include everthing up to the TLD. Obviously, you could have a local address book for looking up the higher levels of the address, so that you wouldn't have to worry about the TLD and its immediate subordinates for your regular contacts - but there is no reason why you should use any part of the DNS name as the lookup key in that dictionary; you could use any identifier. Once you get to the DNS level, the TLD cannot be truncated.
-
W∴ Balboos wrote:
You do know that computers don't give a damn about data format so long as they know how to interpret it.
In that sense, there is no difference between humans and computers. If you give a computer the date 9/11/2001 and tell it "Interpret this as a date in American format", or you do the same to a human, it comes out right. If you tell the computer the date 9/11/2001 and tell it "Interpret tis as a date in European format", you get a different result from the computer, and so you would from a human given the same instruction. What regards DNS names: No, they cannot be truncated. You have to include everthing up to the TLD. Obviously, you could have a local address book for looking up the higher levels of the address, so that you wouldn't have to worry about the TLD and its immediate subordinates for your regular contacts - but there is no reason why you should use any part of the DNS name as the lookup key in that dictionary; you could use any identifier. Once you get to the DNS level, the TLD cannot be truncated.
You really don't get it: YYYYMMDD can be sorted trivially, whether sorted as an integer or a character string (so long as the year contains 4 figures w.r.t. char sorting). The computer can read any of the dates and the overhead for that is the same. But, if sorting the dates, they have to be parsed/interpreted before sorting (or within a custom sorting function - same thing) - and the work is a lot harder . . . unless the formatting of the date is such that it's naturally in order without any parsing/interpretation. As for truncation of DNS - it's something you mentioned. The DNS masks would seem to be a hint as to how things are more likely done - although I'm no expert in that field. Handling native sizes, however, is what will happen in the system, anyway - so (originally, in those days) a 32 bit value is going to be a 32 bit value as it's passed through the 32 bit system/CPU. Unwanted values would be masked, not truncated. But I'll let you claim expertise in that matter.
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010
-
Oh, and Micronesia. At least according to Wikipedia. So why does pretty much every US based service that caters to a worldwide audience use mm/dd/yyyy as a date format Latest example this hour is VS team services "Access issues with Visual Studio Team Services – 5/25 – Investigating". 5/25 = 25 May. That's easy. But when I see 6/7 or 10/8 I have to manually check the site and see what culture they are based in. No one in the US (I'm guessing - apart from ex-pats) worry about this. Or are probably even aware of this issue. Everyone else in every other country is aware of this issue. Everyone in Canada manages to deal with it. And I don't know how their brains don't explode. Canada uses dd/mm/yyyy. Except when it uses mm/dd/yyyy because either it's a US based company, they are using a US based system, they are trying to be nice to their US based customers, because they just forgot to use dd/mm/yyyy or because they know it's me and so they deliberately use an ambiguous date format to do my head in. Date formats in Canada are totally and completely messed up. So: Why, in this day and age, do those in the US, when writing for an international audience, still use mm/dd/yyyy? (And I'll add another one: Why do companies in the US find it impossible to ship outside the US? It's very odd) OK, back to hitting refresh several times a second waiting for Team Services to come back online.
cheers Chris Maunder
You have a couple similar cases, especially in web stores which use software developed in the US, even though they are European stores: Lots of European countries put the ZIP code ahead of the city name, not after the state name, but the address label print routine insists on doing it "The American Way". In Europe, there is a standard for prefixing the zip with a country code (like NO-7035 Trondheim here in Norway). Lots of web stores will not accept this format. If the web store requires a telephone number, I would follow the international standard of adding a prefix "+" and the country code, like "+47" for Norway - the plus sign indicating "Whatever prefix your national telephone system requires for international calls". Lots of web stores refuse to accept the +. In several web stores, I have to repeat either the city name or the country name, because the software insists on a "State" level inbetween. I have even bought stuff from stores insisting on a non-empty "county" name (in addition to the "state" name). Sure, we do have county names in Norway, but they are never used in addressing! However, my biggest frustration has nothing to do with European vs. US style: I have never, ever, had my credit card number accepted the way it is printed on the card: As four groups of four digits! Every single web shop insist on a single 16-digit sequence, which is far more difficult to verify against your card. It would take the programmer one single one-line function call to remove the spaces from a four-times-four digit enty, but not one of them will do that! Usually, the same applies to telephone numbers: You cannot type them the way you normally do, in space or hyphen separated groups of digits. Maybe one in four will allow spaces/hyphens, serving as a proof that it is possible to remove them programmatically....
-
Oh, and Micronesia. At least according to Wikipedia. So why does pretty much every US based service that caters to a worldwide audience use mm/dd/yyyy as a date format Latest example this hour is VS team services "Access issues with Visual Studio Team Services – 5/25 – Investigating". 5/25 = 25 May. That's easy. But when I see 6/7 or 10/8 I have to manually check the site and see what culture they are based in. No one in the US (I'm guessing - apart from ex-pats) worry about this. Or are probably even aware of this issue. Everyone else in every other country is aware of this issue. Everyone in Canada manages to deal with it. And I don't know how their brains don't explode. Canada uses dd/mm/yyyy. Except when it uses mm/dd/yyyy because either it's a US based company, they are using a US based system, they are trying to be nice to their US based customers, because they just forgot to use dd/mm/yyyy or because they know it's me and so they deliberately use an ambiguous date format to do my head in. Date formats in Canada are totally and completely messed up. So: Why, in this day and age, do those in the US, when writing for an international audience, still use mm/dd/yyyy? (And I'll add another one: Why do companies in the US find it impossible to ship outside the US? It's very odd) OK, back to hitting refresh several times a second waiting for Team Services to come back online.
cheers Chris Maunder
-
Oh, and Micronesia. At least according to Wikipedia. So why does pretty much every US based service that caters to a worldwide audience use mm/dd/yyyy as a date format Latest example this hour is VS team services "Access issues with Visual Studio Team Services – 5/25 – Investigating". 5/25 = 25 May. That's easy. But when I see 6/7 or 10/8 I have to manually check the site and see what culture they are based in. No one in the US (I'm guessing - apart from ex-pats) worry about this. Or are probably even aware of this issue. Everyone else in every other country is aware of this issue. Everyone in Canada manages to deal with it. And I don't know how their brains don't explode. Canada uses dd/mm/yyyy. Except when it uses mm/dd/yyyy because either it's a US based company, they are using a US based system, they are trying to be nice to their US based customers, because they just forgot to use dd/mm/yyyy or because they know it's me and so they deliberately use an ambiguous date format to do my head in. Date formats in Canada are totally and completely messed up. So: Why, in this day and age, do those in the US, when writing for an international audience, still use mm/dd/yyyy? (And I'll add another one: Why do companies in the US find it impossible to ship outside the US? It's very odd) OK, back to hitting refresh several times a second waiting for Team Services to come back online.
cheers Chris Maunder
Amazing that you're not railing against the focus on Arabic numerals; what about all of those people in the international community that use alternative counting systems? Or other-than-lunar calendars? How, in this day and age, are we overlooking the people that believe that time as it is understood is meaningless, and express the date as "today". :-D Honestly, though, I'm more curious as you why anyone in their right mind would think that dd/mm is better. It has all the same problems, is equally stupid, and is just as reliant on cultural knowledge. If we're going to reformat, I hope it would be to ddMMMyyyy to bludgeon understanding into people (that do believe in time, anyway). In the end, though, I will not have an agenda of changing the common cultural norm (I'm just not that invested) so I'm going to go with the old row: "It ain't broke, so I'm not going to fix it."
"There are three kinds of lies: lies, damned lies and statistics." - Benjamin Disraeli
-
You really don't get it: YYYYMMDD can be sorted trivially, whether sorted as an integer or a character string (so long as the year contains 4 figures w.r.t. char sorting). The computer can read any of the dates and the overhead for that is the same. But, if sorting the dates, they have to be parsed/interpreted before sorting (or within a custom sorting function - same thing) - and the work is a lot harder . . . unless the formatting of the date is such that it's naturally in order without any parsing/interpretation. As for truncation of DNS - it's something you mentioned. The DNS masks would seem to be a hint as to how things are more likely done - although I'm no expert in that field. Handling native sizes, however, is what will happen in the system, anyway - so (originally, in those days) a 32 bit value is going to be a 32 bit value as it's passed through the 32 bit system/CPU. Unwanted values would be masked, not truncated. But I'll let you claim expertise in that matter.
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010
"Trivially" under a number of conditions. You state one of them yourself: The year must always be specified in a four digit format. That isn't always done (look at the expiration date of your plastic card!). Second: People find an 8-digit sequence hard to read, and won't accept that machine oriented format you specify, but split it up. One date split with slashes, 2001/09/11, and another with hyphens, 2016-05-26, do not sort trivially (beyond the year) until you remove the separators that you simply must allow for readability. And then pops another issue up: 2016-5-16 will not trivially sort correct with 2016-05-26. Many people do not number months in their daily life, but would like to write 2016-May-26. Then you mess up the soring completely... As long as you insist on forcing onto ordinary people what they don't want, but you insist that it suits the computer better, you end up like the Linux success on the desktop: People choose something else, something that matches their preferences and conventions better.
-
Not to mention time zones, winter and summer time, formatting, parsing, the time part of dates, leap years, different ranges in different types/systems, timespans vs. datetimes... Yeah, it's about time someone lost his mind X|
Read my (free) ebook Object-Oriented Programming in C# Succinctly. Visit my blog at Sander's bits - Writing the code you need. Or read my articles here on CodeProject.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
+1 to time! Why the hell we should deal with these idiotic am/pm/fm/zm?? Just to say 23:17 and viola - everybody knows when it is! Same with "timezones" - another world-wide stupidity! One time can fit all. Who care I wake up at 8:00 or 23:00?? If daylight in my country will be from 23:00...15:00, it won't affect my life even on a cent. So when it's 17:23 in England, let it be everywhere! In any case before calling my friend in Japan I confirm they have daytime. This unification immediately simplifies a lot of schedules and calculations (hi, DBMS!). When you depart from Australia at 3:00, you arrive _at_calculable_time_ in US and you don't have to think how much hours is difference between timezones.
-
"Trivially" under a number of conditions. You state one of them yourself: The year must always be specified in a four digit format. That isn't always done (look at the expiration date of your plastic card!). Second: People find an 8-digit sequence hard to read, and won't accept that machine oriented format you specify, but split it up. One date split with slashes, 2001/09/11, and another with hyphens, 2016-05-26, do not sort trivially (beyond the year) until you remove the separators that you simply must allow for readability. And then pops another issue up: 2016-5-16 will not trivially sort correct with 2016-05-26. Many people do not number months in their daily life, but would like to write 2016-May-26. Then you mess up the soring completely... As long as you insist on forcing onto ordinary people what they don't want, but you insist that it suits the computer better, you end up like the Linux success on the desktop: People choose something else, something that matches their preferences and conventions better.
First, the hypen and slash delimited versions of YYYYMMDD still sort trivially as text. But let's get to the real point. Go back to my original posting (reply) way up at the top of the thread. I said I use YYYYMMDD . You can come up with any number of ways that things won't work - but if they don't follow the above then their relevance is, well, none.
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010
-
You do know that computers don't give a damn about data format so long as they know how to interpret it. Why the DNS order is like it is? Truncation would make a good reason: it's as easy to truncate the front as the back (same, to, with masking, so far as that goes). If there's to be any controversy as to why either choice, I'd look at the every famous Motorola vs. Intel format for storage of numerical values: Big Endian vs. Little Endian. Both work - so long as you know what's coming. Now for the date formatting which I noted, above, one could argue that the US method is better if you leave off the year (not uncommon) for then it can be sorted naturally. The Euro-system is part of the same Obsessive-Compulsive disaster that brought on the metric system. I draw your attention to the following that you may realize the error of your ways: The Lounge - CodeProject[^] and even in my youth, oh so many years ago, The Lounge - CodeProject[^]
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010
Really? Is the metric system a disaster? So you consider that using fractions of 10th 0.001 mm = 1 micrometer 1 mm 10 mm = 1 centimeter 100 mm = 1 decimeter 1000 mm = 1 meter 1000000 mm = 1000 mt = 1 kilometer is a mess? Vs 1/2", 1/4", 1/8"....1/64".. 1/256", 1'-3/16", 23 yards 2' - 5/32" 1 mile = 1760 yd???; 1 yd = 3 feet???; 1 feet = 12 inches??? 1760 - 3 - 12 Really? I really don't think the imperial system is much clear to a person that never have used this measurement system. The other one is much logical to our brains. Maybe the base-10 numeric system is not the best, but we at our actual civilization adopted it (Including the imperial units users), maybe because we have 10 fingers on our hands? For whatever reason, our occidental brains think in 10, so I think that the metric system is an approximation to our feeling, not a disaster!!
-
Really? Is the metric system a disaster? So you consider that using fractions of 10th 0.001 mm = 1 micrometer 1 mm 10 mm = 1 centimeter 100 mm = 1 decimeter 1000 mm = 1 meter 1000000 mm = 1000 mt = 1 kilometer is a mess? Vs 1/2", 1/4", 1/8"....1/64".. 1/256", 1'-3/16", 23 yards 2' - 5/32" 1 mile = 1760 yd???; 1 yd = 3 feet???; 1 feet = 12 inches??? 1760 - 3 - 12 Really? I really don't think the imperial system is much clear to a person that never have used this measurement system. The other one is much logical to our brains. Maybe the base-10 numeric system is not the best, but we at our actual civilization adopted it (Including the imperial units users), maybe because we have 10 fingers on our hands? For whatever reason, our occidental brains think in 10, so I think that the metric system is an approximation to our feeling, not a disaster!!
You seemed to have missed the point. This is CP - we do computer stuff (and some drink Gin). The weights/measures I specified are all powers of 2 - very computer friendly for inter-conversion. On a historical basis, note that you happen to use base ten for that metric trash because you've ten fingers. For a century or two, those more enlightened[^] (i.e., they didn't need to count on their fingers) argued for a switch to base-12 for everything. The reason? 10 has two factors besides itself and one: 2, 5 12 has four factors: 2, 3, 4 and 6 The factors are used in more typical human-friendly transactions 1/2, 1/4, 1/3, for example. So, you guys keep counting on your fingers whilst we embrace our current reality and look to the future!
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010
-
You do know that computers don't give a damn about data format so long as they know how to interpret it. Why the DNS order is like it is? Truncation would make a good reason: it's as easy to truncate the front as the back (same, to, with masking, so far as that goes). If there's to be any controversy as to why either choice, I'd look at the every famous Motorola vs. Intel format for storage of numerical values: Big Endian vs. Little Endian. Both work - so long as you know what's coming. Now for the date formatting which I noted, above, one could argue that the US method is better if you leave off the year (not uncommon) for then it can be sorted naturally. The Euro-system is part of the same Obsessive-Compulsive disaster that brought on the metric system. I draw your attention to the following that you may realize the error of your ways: The Lounge - CodeProject[^] and even in my youth, oh so many years ago, The Lounge - CodeProject[^]
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010
Natural sorting is only advantageous to computers, and they don't deal with partial dates. I can't remember ever needing to write code that handled dates in the form of strings that didn't even include the year. So that's not really a bonus. Come on, admit it: the US convention simply makes very poor sense - a fact supported by the fact that almost the entire rest of the world does it the other way round. Also, the metric system is great, not sure what you've got against that as well.
