|
So you know how to write code in Visual Studio but you have never learned the basics of a Dialog Box?
|
|
|
|
|
|
Very interesting, but nothing to do with your problem.
|
|
|
|
|
My fellow Americans,
In your experience what websites have good deals on fireworks?
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
Hey!
Take it to the Soapbox!
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Mark_Wallace wrote: Take it to the Soapbox!
Is this topic too explosive for you?
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
Adobe[^]. 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Funny! I used to use it (the Macromedia version) frequently but it didn't make the cut on the last development rigs...mostly due to the fact that it doesn't play nice with Aero. I'm trying Gimp to replace it...so far, so good, but I haven't done much with it (gimp) yet. 
"Go forth into the source" - Neal Morse
|
|
|
|
|
Gimp is pretty powerful, and I like it. There is also Gimpshop | The Photoshop Free Alternative[^], and a photoshop layout from PortableApps.com[^]
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
|
|
|
|
|
This is why I asked the Americans to answer. 
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
Buy anything from oracle for me and you'll see my fireworks go off from the US 
|
|
|
|
|
|
I wonder what that would sound like in space.
Marc
|
|
|
|
|
You could do nothing but watch silently
|
|
|
|
|
That's interesting ! I really like Between Music's "Bones of Bruised Houses:" [^].
cheers, Bill
«There is a spectrum, from "clearly desirable behaviour," to "possibly dodgy behavior that still makes some sense," to "clearly undesirable behavior." We try to make the latter into warnings or, better, errors. But stuff that is in the middle category you don’t want to restrict unless there is a clear way to work around it.» Eric Lippert, May 14, 2008
|
|
|
|
|
I should really check out more of them 
|
|
|
|
|
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
|
|
|
|
|
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.
| 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 |
|
|
|
|
|
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[^]
| 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 |
|
|
|
|
|
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.
| 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 |
|
|
|
|
|
"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.
| 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 |
|
|
|
|
|
W∴ Balboos wrote: First, the hypen and slash delimited versions of YYYYMMDD still sort trivially as text.
Sure - as long as everybody uses the same separator. But not everyone does.
Finding a truly trivial sorting problem is not a trivial task... Especially not in multi-national environments. You believe that alphabetic sorting is trivial? What about a common Scandianvian telephone book with Norwegian and Swedish names? The Norwegian alphabet goes ...wxyzæøå, while the Swedish goes ...wxyzåäö - the ä and æ are (from both sides) considered the same letter, as is ö and ø. So where should å be sorted: Before æø or after æø?
Or French, where you sort by the alphabetic character as the primary key, but two words differ in accents (which quite often is the case in French), they are not identical, and the sort order of the accents, as a secondary key, is well defined. Or Spanish, where certain double letters are sorted as a single letter, but not in an identical manner: I believe (disclaimer: I cannot speak Spanish myself) that ll is one case: The double ll is sorted as a if it were a single letter between l and m in the alphabet.
These details does not relate to your highly "synthetic" format that is not acceptable for use by common man. It is nothing but a lab prototype. That is what I wanted to stress as "the real point".
We could simplify sorting of dates by using the day number of the year - abandoning months and day within month completely: Problem solved!
Or we could use Unix epoch: Geek & Poke, 20081221[^]
(For those who have not yet discovered Geek & Poke: That is the greatest source of computer geek humour I have ever seen!)
Obviously, a list of eight digit decimal numbers can be trivially sorted. But is is about as useless as sorting a ten digit number such as 1229883309. Well, not quite, but if people won't accept that eight digit decimal number, then it is of no help that it will trivially sort.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
