|
Sorry to disappoint you. I have travelled widely, all over the world. My wife is an "Anglophile" of the first order and magnitude. I have met "Brits" in London, Bermuda, and Hong Kong and the United States. I brought in New Year 1970 getting drunk in Hong Kong with British soldiers (and yes they drank me under the table, and out the door). They were the exceptions to the rule which I mentioned earlier.
While my comments were partially "Tongue in cheek" and meant to get a rise out of you, which they apparently did, (did I mention I am 1/2 Irish? ), I assure you there is a very large nugget of truth in them. And I stand firmly by my earlier comments.
The fact that you replied by lecturing me about judging a nationality based on an assumption that I had not met many British people, just tends to prove my remarks about arrogance and pomposity. 
I am sure we could become great friends, given the chance. I sincerely apologize for any hurt feelings I may have caused you. Why, I have had Scotties and Westies as pets for 40 years, or so!
BTW: I openly admit to being quite arrogant and pompous myself.  In fact I am rather proud of it. In any event, Us old guys (Are you really older than me? I thought I was the only one still working in the business at my age) should stick together, not argue. There IS still that Irish, English thing, I guess....
Well Toodles for now.....
It's a random chance universe and we are all just riding waves of probability...
|
|
|
|
|
I certainly don't recognize what you are referring to, arguing in favor of yyyymmdd sort of as opposed to some "Eurogance". ISO 8601 has been adopted in Europe to a much higher degree than in the US, many years ago.
Obviously, thirty years ago (when ISO 8601 was first published) there were other ways of writing dates. Some schemes were integrated in formal systems, such as the Norwegian "fødseslsnummer" (birth number, a rough equivalent to the social security number in the USA) where the person's ddmmyy birth date make up 6 of the 11 digits. When ISO 8601 was introduced, this 20+ year old scheme was not changed, and still remains. But for the great majority of new schemes established after 1988, the yyyy-mm-dd (with the hyphens, according to the international standard) format is used. Obviously, ISO 8601 was not out of the blue, either: The 8601 format was well known even before 1988.
In informal contexts and particularly orally, other schemes (such as "thirteenth of June") is still in use. In formal contexts, ISO 8601 has a very strong position (unless old conventions must be followed, such as the fødselsnummer).
Note that when Europeans do 8601, they do 8601: With the hyphens. Not as an 8-digit string. Not with slashes, but according to the international standard.
|
|
|
|
|
Member 7989122 wrote: dopted in Europe to a much higher degree
Worthless subjective conjecture - since I see Euro-dates always as DD-MM-YYYY on, for example, broadcast media (EuroNews, and others) - what you say is non-sense, or as I prefer to put it, yet another example of Eurogance.
Member 7989122 wrote: Note that when Europeans do 8601, they do 8601: With the hyphens.
More Eurogance. If one does ISO 8601 it follows such standards and not others. Otherwise, it doesn't follow the standards.
As for yyyy/mm/dd: I've never seen it in the US. It MUST be a European thing. (did you know we don't all wear stetsons and string ties?)
Look at the phraseology of your post - how you attempt to make the European usage better with vague claims. Always with the implication that you must be doing it better than the US. A clear sign of the psychological impotence of your position and the progenitor of Eurogance.
| Ravings en masse^ |
|---|
| "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 |
|
|
|
|
|
I have lived long enough to see ISO 8601 replacing older schemes in lots of areas.
I have even seen old "Imperial" units being replaced with metric units. (When I was a boy, we counted eggs by the score, and my birth certificate states my birth weight in pounds.)
If you come in to take a snapshot right now, you don't see the direction in which things are moving. Especially if you have the attitude that "The European way is so-and-so", you can find evidence for that, without knowing what is bound by legacy and which is the preferred way when establishing something new.
Furthermore, it seems like you fail to distinguish between informal speech, informal text, and formal, "technical" uses. Like, you may hear a European carpenter refer to a two-by-four in speech, but in all papers, it says 48 by 98 mm (it isn't even two and four times 25.5 mm!). He may refer to his ruler as his "inch-rod", even though the inch marks dissapeared a generation ago. All time-of-day values, e.g. in train/boat/plane schedules are given in 24h format, yet lots of people use 12h format in informal speech: "Meet me around seven, OK?"
Europe has largely accepted both the metric system, 24h times, and ISO 8601 format for all formal use. Obviously, in informal contexts, old conventions will not die out overnight, like references to Imperial units are informally used a hundred years after they were abandoned. Yet everybody knows that the unambiguous, formal formats, whether 24h, metric or yyyy-mm-dd is expected in reports, orders, schedules, ... We have no objections to them; we do not fight them. You introduce yourself as "John Doe", but accept that in registries, you are known as "Doe, John". When asked when you were born, you reply "Fourth of July in 1976", but when filling in a form, you have no objections to the "1976-07-04" format.
I have not seen any similar movement in the US culture, neither towards metric units, 24h clock nor ISO 8601 dates. To the contrary: You regularly see/hear people turning their back to the metric and international formats, with a rejecting "But why??, often with several arguments to support the old US way. The armed forces are fond of 24h clock, but the civil society still clings to AM/PM. To Imperial units. To June, 13th, 2018.
And you are right: Slashes are not uses with yyyymmdd, but with mmddyy: 6/13/18 (or mmddyyyy: 6/13/2018), That is in the US. Some other English-speaking countries do it in another order. (Date and time notation in the United States[^]
|
|
|
|
|
The website reported a fatal error when I posted the above message, and the message didn't show up when CP again responded. So I wrote the answer below. After posting that reply, the first one popped up. Pick your choice in which one you will read 
|
|
|
|
|
Europeans carry lots of legacy. Norway went metric 143 years ago; still carpenters may refer to a two-by-four. But they know that it is not two by four inches, but 48 by 98 mm. Their yardstick (or inchstick, in Norwegian lore) lost the inch markings a generation ago, but the name of the tool remains. You introduce yourself as "John Doe", knowing that in formal registers you are listed as "Doe, John". You say "Meet me around seven", well knowing that in your calender, you write the appointment as 19:00. When asked about your birthdate, you may answer "seventeenth of May, 1976", but when filling in a registration form, 1976-05-17 is usually the expected format.
Old traditions survive in informal context, some times for generations after new forms have completely taken over in formal contexts. I am old enough to see the last remains of Imperial units disappearing, 24h clock time becoming more dominant, and: A rapid growth in the use of ISO 8601 formats.
The important thing is not that people use a variety of old formats in informal speech and text, but the general acceptance of both metric units, 24h clock and ISO 8601 formats in formal contexts. Noone rises an eyebrow at any of these: They are logical, unambiguous, standard. They are welcomed.
That is definitely not my impression of, say, the US civil population. The armed forces have accepted 24h clock, and to some degree metric units, but civil USAnians tend to kick and scream to the slightest hint about abolishing Imperial units, am/pm or the June 13, 2018 format. It is a repeat of the old "The customer can get the T-Ford in any color he wants, if he wants it in black". A standard date format would be welcomed by most Americans, provided it conincides with the format they have always used. If there is any movement towards ISO 8601 in the USA, or the metric system, or 24h clock (which is implied by ISO 8601), it certainly hasn't reached the news.
Obviously, old forms will be used informally in the USA if ISO 8601, metric units etc. are introduced in all formal contexts, just like in Europe. I very rarely, if ever, meet USAnians who say "That's fine with me", but I have met quite a few giving me a stream of arguments why changing anything at all would be a very, very bad idea, even in formal contexts. Europe wants it, USA does not want it, even if "allowed" to use the old formats in informal speech and texts.
If you think that the civil society in the USA is ready to embrace ISO 8601 and its 24h clock, and maybe metric units as well, I am curious to see clear evidence of this.
(You are of course right that yyyy/mm/dd is not used in the USA, but mm/dd/yy or mm/dd/yyyy certainly is - Date and time notation in the United States. Some other countries using slashes put the units in another order; you must know the origin of the date to interpret it.)
|
|
|
|
|
Actually, when it comes to dates the US population is VERY consistent: I have NEVER heard anyone say "I was born the seventeenth of May, 1976." An American would say "I was born May 17, 1976" which is also the way the date is written only using numbers instead "05/17/1976". We read numbers left-to-right, as well: 457 is "four hundred fifty seven" not "four hundred seven and fifty" as some European languages would have it (German).
The USA has attempted to implement metric several times. Weather forecasts have tried converting to Celsius; however, Americans realize the worthlessness of a system where 20 degrees might require a light jacket but 25 is t-shirt weather: the granularity is insufficient. Liquid has made substantial progress primarily due to two-liter bottles of soda; however, gasoline and milk tend to be sold in gallons. In reality, any unit is fine to simply compare prices: we have accepted gallons. Distance conversion is economically unworkable: all of our traffic signs for distances, exits, etc. are miles. Such conversion would cost a fortune, and accomplish what?
If the proposal is that the USA should convert to better facilitate visitors from foreign countries, I would suggest Europe should post mileage and Fahrenheit temperature because I suspect more Americans visit Europe than vice versa.
Dates should be YYYY-MM-DD HH:MM:SS using twenty four hour time. Then we just have to argue whether that is local time or UTC.
|
|
|
|
|
Greg Lovekamp wrote: Americans realize the worthlessness of a system where 20 degrees might require a light jacket but 25 is t-shirt weather: the granularity is insufficient.
Funny how often this about granularity comes up in the C/F discussion, and almost never in other cases!
I have tried to point out to USAians the finer granularity of km over miles (the difference is in the same range as F vs C); it doesn't stick. I have pointer out the lack of granularity of the US dollar compared to numerous other currencies (in particual before the Euro was introduced), and the USAinas protest: But we have got cents! Sure you have. And I have heard US weather forcasts claiming that there is a 57.14 percent chance of rain tomorrow (I am serious! Two fractional digits in a percentage of probability), so you sure can handle decimals! If you really need four digits precision in the chance of rain, then you certainly could handle fractional degrees as well. All my electronic thermometers (I've got at least six or eight) can be switched to F degrees, and they all have a resolution of 0.1 F. If whole F-degrees were sufficient, there should be no need for any fractional part!
Here in Norway, we often refer to half-degrees (it is twenty and a half outside right now), and we always did. That is better resolution than whole F degrees. Regardless: The level raise of the mercury or blue-colored spirit column, or movement of the arrow, is exactly the same for a given temprature change; the difference lies only in the distance between the tick marks next to it.
And then: Set two cheap thermometers (of two different makes) side by side, and after they have stabilized, compare the reading. They may differ by far more than even a centigrade! (More expensive, newer thermometers may be more exact, but not the ten and twenty year olds you find around in your parent's house). Maybe they are fairly stable, the one always showing 70F while the other shows 68F, but you don't know which corresponds to the weather forecast predictions.
Furthermore: I have never met any person who can tell if the air is 68F or 69F, without any refernce point or thermometer. (If that was a common ability, why would we need thermometers to tell us what whe can feel anyway?) Wind, humidity and the temperature in the envionment we came from makes far more change than a couple of degrees.
Actually, this "granulatity" argument for F-degrees is rather artificial; you don't really need or make use of it. Except when you need an argument for keeping things the way they have always been, rejecting any change.
That is quite typical: If you simply don't want to change, you make up arguments that you never consider otherwise. That is not particular to USAnisans; everybody does. But it becomes quite visible in the case of changing units.
An old story (quite a few people even claims that it is true) from Norway is when the hymnal used in the protestantic church was to be replaced by a new version: In one of the parish councils, one prominent memeber stood up and declared that he certainly welcomed the new hymnal, but out of respect for the all the old people who had grown up with the old one, the introduction of the new versioun should wait until all the old people had died. ... As we say in Norway: If it isn't true, it sure is a good lie! It perfectly illustrates how we mindlessly can use almost any argument to resist a change we don't want.
|
|
|
|
|
You raise some very valid points about people everywhere being unwilling to change. Nonetheless, the primary question remains: in what way will the change benefit those whom the change is being forced upon? Was it easier to find a particular hymn in the new hymnal? Or was it simply that everyone should change due to a particular person's whim?
In a country where everyone understands Fahrenheit and statute miles, what advantage is provided to citizens by changing to Celsius and meters?
|
|
|
|
|
Not that it matters for the principles discussed here, but to fill in the details:
The old hymnal, dated 1870, was an attempt to merge three older hymnals (the oldest one from 1699) into a common one for all congregations of The Church of Norway. Consider it a "beta release": Which hymns would actually be used, when a much richer selection was provided? A number of hymns were translated from German and Danish into Norwegian for the new hymnal (Danish and German had been 'church languages' for ages, but were being displaced by Norwegian.) Writing new hymns was a popular activity among poets and composers. So, in 1926, a revision was published, with the never-used hymns removed and a lot new hymns added. It was left to the congregations when to switch to the revised hymnal, some clung to the old versions for 10, 20 or 30 years. So, the benefit of the new hymnal was to have all the hymns being used in a single volume, and not too many obscure, forgotten hymns.
Advantages of metric system? The obvious one: Everybody else is using it. The question of convenience: Regularity. If the road measures 34 mm on a 1:1000.000 map, how many kilometers is that? If it measures 1 3/8 in, how many miles is that? What is the speed of light, measured by furlongs per forthnight?
The majority of scientific values, such as density of some matter, temperature etc. is stated in units that can be processed directly within the metric system. Temperature differences are stated in Kelvin, of the same granularity as Celsius; absolute temperatures in Kelvins above absolute zero. You never have to multiply by arbitrary factors of, say, 3 or 7 or 12, because of the choice of units (obviously, a given matter has properties like water requiring 4.2 kJ for heating 1 kG by 1 K, but the 4.2 factor is not from how units are defined).
One specific example (from my own house remodeling project): In building construction, the heat flow through a wall, a window etc. is indicated by its U value. Norwegian regulations require U < 0.18 for walls of new residental houses. How much is the heat loss through a wall of 2.50 by 4 meters when the temperature outside is -30C and the indoor temperature is 20C? U * area * deltaT, 0.18 * (2.5*4) * (20-(-30)) = 90 W. (Measure that wall in feet and inches, and state the temperatures in F, and see if the calculation is that simple!) -- The U values is per surface unit. For a given insulation, the 'lambda value' is specified: Multiply it by the thickness of the insulation to get the U value - whether you measure by mm, cm, or m. You just move the decimal points; the digits are unchanged.
Simple multiplication/addition of well known values, with no 'magic factors', no 1/8-of a unit, no 'how many yards to a mile?', no units that depends on what you measure... The metric calculations are so much more transparent and non-magic; you can grasp them easily. And you can relate to them. Even though I cannot off hand tell you how large a soccer field is in square meters, if you tell me that it is 100 by 60 meters, I immediately relate to it as 6000 square meters, which is five times the size of my garden lot. If some area is specified as the size of ten football fields, neither I nor very many others immediatly know how much that is in square foot or acres; it isn't transparent in the same way.
As long as a given unit is used alone, never related to other units (say, inches never related to miles) and the reading is used 'as is' and that is is, then any unit that 'everyone understands' is fine. The great advantage of the metric system is when you combine different measures. If you want to saw that new football field with grass seeds, and the seed vendor tells you to use so-and-so many grains (as a weight unit) of seed per square foot, how many pounds of seed will you need? In principle, you make the same calculation as with metric units, yet it involves a fair number of extra factors that you will have to know of.
Imperial units has one great value: You have to make so many extra multiplications and divisions that you really learn to do those operations - moving the decimal point doesn't give you nearly as much math drill. But you have this advantage only if you actually make the calculations regularly, such as measuring on the map in 1/8 in units to determine the distance in miles, and the time to drive that distance at a speed of x furlongs per forthnight. If you just read the value and to not convert it, you loose this advantage.
modified 20-Jun-18 4:24am.
|
|
|
|
|
As far as the hymnal, one thing that NEEDS to be recognized is that there WAS a loss: some hymns were dropped. Perhaps that was better for the many, but just perhaps not for the particular holdout congregation.
The rest of your narrative is written from the perspective of someone raised in the metric system. For you, it is simple. For me, it is simple; I did a lot of metric calculations in college physics, but thirty-five years later, not so much. I think for anyone it is simple, but that simplicity is irrelevant in light of requiring EVERYTHING to change.
In USA, we do not do many conversions from inches to miles. Things that are smaller area are measured in feet: carpeting, hardwood flooring, etc., is normally priced by square feet, occasionally by square yard. The sizes of the numbers, however, rarely cause mental anguish when that division by 9 must occur. Large distances are by miles. Maps are normally something like 1/8" is equal to one mile, and with today's technology, the electronic maps will tell you without looking at a printed map anyway.
It is entirely possible that it is a uniquely American thing that we don't really need such precision. If I am taking a 100 mile trip, I don't care about that last inch and a half. In fact, we don't really get too precise on the number of miles. I can't tell you if the closest major city to my home is 88 miles or 109: it's about a hundred. It will take more than an hour to get there, but probably no more than a hour and a half.
Our culture has specialists who deal with their particular units of measure. For example, some people sell carpeting; tell them how big your room is, they quote a price. Check around with a few such experts and pick the best deal. If you are moving across country, you check with several moving companies, you get several price quotes and again, pick the best deal. The American system is all about capitalism; create a product or service cheap enough that someone will pay you rather than do it themselves.
Changing the status quo to metric just because "everybody else is using it" is simply not going to fly; there is no ADVANTAGE to change for the average American. In a capitalist world, "if there is no advantage for me, I am opposed to it." That is, in essence, America. It is a different perspective, I think, from European attitudes, but hopefully that let's you know why it will probably never occur.
|
|
|
|
|
Whichever one we're using, that's the right one. The rest of y'all can adjust. 
Sometimes the true reward for completing a task is not the money, but instead the satisfaction of a job well done. But it's usually the money.
|
|
|
|
|
Exactly, that's what we say.
|
|
|
|
|
Vunic wrote: But why? Why not we fix this in peoples minds and make them follow a unified type.
Same reason as any dispute in history - people disagree. I view the format from the perspective of importance. I care more about what relative day it is (Mon-Sun) than literal day and place more value on the month (year is obvious) so MM-DD-YY makes more sense, but many would disagree with this because they place value elsewhere.
EDIT: As Richard shows above 
|
|
|
|
|
|
Because it's DD-MM-YYYY, everything else is pathetic
Rules for the FOSW ![ ^]
if(!string.IsNullOrWhiteSpace(_signature))
{
MessageBox.Show("This is my signature: " + Environment.NewLine + _signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
As Jochen said, ISO 8601 is the standard - and it insists (correctly) on four digit years, not just two. Remember the Millenium Bug problem and the amount of work that caused?
Just use yyyy-MM-dd and it'll be right.
Sent from my Amstrad PC 1640
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
OriginalGriff wrote: Remember the Millenium Bug problem and the amount of work that caused profiteering that that enabled?
98.4% of statistics are made up on the spot.
|
|
|
|
|
Some of it was profiteering, yes - but a lot was behind the scenes and wasn't.
I spent a lot of time, effort, (and money) in late 90's making sure that all the systems in company I had just joined as Technical Manager (i.e. responsible for everything more complicated than a mains plug) were going to work on Jan 1st 2000, and replacing those that wouldn't. And that meant exhaustive testing on the Unix box that ran the company accounts (Accounts software: fail. Accounts system OS: fail. Accounts system hardware: Oh ![Elephant | [mastadon]](https://www.codeproject.com/script/Forums/Images/elephant.gif) , Oh , Oh , fail, fail, fail. Can I get it back up by Monday?) followed by new software selection, implementation, data transfer, training, and parallel running as well as new software to produce management accounts summaries in a format they could understand.
The reason very little failed on Jan 1 worldwide was that a huge amount of effort went into making sure they wouldn't ...
Sent from my Amstrad PC 1640
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
It was a fair bit of both, in truth.
Yes, there was an awful lot of genuine work involved but equally there were an awful lot of "consultants" lining their pockets by spreading the fear.
For my part, I did very well out of it working on a project for a very large organisation to temporarily migrate their ERP system for the two years across the millennium because SAP were reluctant to guarantee millennium compliance. Was that money well spent? I rather suspect that any problems arising from not doing it could have been sorted out by a bit of overtime for the finance team. Either way, I was rather glad that developers of yore were so short-sighted and/or strapped for disk-space!
98.4% of statistics are made up on the spot.
|
|
|
|
|
I am surprised because SAP was touted as the solution to the Y2K problem in the US and was bought by many customers.
|
|
|
|
|
As I remember it (and it does seem like an awful long time ago, now!), they were a bit slow off the mark in making any guarantees - at least in the UK. I'm pretty sure that they eventually did but by that time our client had already committed to take the route that they did - running through the timeline in my head, I suspect the decision was made sometime during 1995.
98.4% of statistics are made up on the spot.
|
|
|
|
|
I also ended up correcting a fair number of serious bugs in my company's software related to this issue. Regrettably, no profiteering on my part, since I was salary. Maybe next time, in the unlikely event its still necessary, when the original 32 bit Unix clock runs out in 2038 
|
|
|
|
|
As I recall, a number of other non-year-2000 bugs were discovered and resolved too.
|
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
![Java | [Coffee]](https://codeproject.freetls.fastly.net/script/Forums/Images/coffee.gif)