The greatest software design blunders of all time
-
dojohansen wrote:
I am saying it's stupid not to let the user who's attempting to log on to choose the locale he or she wishes to use for the login attempt
And all I'm saying is that it's stupid to have all locales installed on all PC all over the world just in case somebody didn't configure his PC to support his password preferences.
dojohansen wrote:
I suppose it's too much to ask for Americans to understand the first thing about locale-related problems
Yeah, blame Americans, seems reasonable :) But this should go in Soap Box/Back Room.
dojohansen wrote:
If you would be kind enough to explain to me why choosing ANY locale that the machine is ABLE to support just for login would be a "blunder" I am all ears.
I specifically referred to installing locales using log-in screen, but hey why should you bother to understand what people are saying when can rant.
Mladen Jankovic wrote:
I specifically referred to installing locales using log-in screen
Yes, implying I had said so too. I did say "add locales", so perhaps it's understandable that you missed what I meant: to the list shown to the user trying to log on. Your reply was nevertheless very much against the spirit of the thread, which was to make our own mistakes seem more reasonable. I guess you just didn't see the humour in it. As for this specific design, I don't know why my XP doesn't show the "NO" locale (though from what someone else posted it seems there's a login user and the locales associated with this user will be displayed), but I know it's installed.
-
I'd have to say MS Access. It just sucks. I'm currently working on a project to convert several Access97 databases and programs into C# and SQL Server. Been going on two years now. Just when I think I'm done, I'm not. It just won't die. X|
-NP Never underestimate the creativity of the end-user.
I like the reporting in access, but the rest of it can die a horrible death!
- S 50 cups of coffee and you know it's on! Code, follow, or get out of the way.
-
I like the reporting in access, but the rest of it can die a horrible death!
- S 50 cups of coffee and you know it's on! Code, follow, or get out of the way.
It's out of the box edit grid does more than the asp.net equivalent in that access's will create a dropdown box for a foreign key lookup table via the gui vs having to manually muck around and edit the aspx itself. Discovering that blew my the time estimate for my first asp.net app out of the water; since I had assumed it would be least as capable as a 10yo POS application. :doh:
The latest nation. Procrastination.
-
It's out of the box edit grid does more than the asp.net equivalent in that access's will create a dropdown box for a foreign key lookup table via the gui vs having to manually muck around and edit the aspx itself. Discovering that blew my the time estimate for my first asp.net app out of the water; since I had assumed it would be least as capable as a 10yo POS application. :doh:
The latest nation. Procrastination.
Not sure if you can really compare Access vs. ASP.NET, but yeah, Access does a lot of the nitty gritty stuff for you, allowing a bubble gum chewing secretary to look like a computer genius to the boss! :-D
- S 50 cups of coffee and you know it's on! Code, follow, or get out of the way.
