Martin Karne on 28/12/2010 at 11:13
Geeeez sorry...
Jizz.
Koki on 28/12/2010 at 11:38
In before deth- oh damn
In before Yako- FUCK
Yakoob on 28/12/2010 at 14:49
Quote Posted by Koki
In before deth- oh damn
In before Yako- FUCK
You're not on top of your shit today are you? Probably could have posted this faster if it wasn't for your computer's crappy UI slowing you down.
CCCToad on 28/12/2010 at 18:17
Quote:
2. Keep the pop-ups and "helpful tips" to a minimum. No, I don't want to take a tour, and no I don't want to clean up my desktop that has five icons on it.
3. Do not assume the user is an idiot by default. This means not hiding access to advanced things (like the console in games). It is just annoying and nobody ever destroyed their PC by typing some incorrect commands into a console window in a game.
4. Do not try and hide the "complexities" of a PC from the user. This means stop hiding those file types by default! All I want to do is rename a txt to a cfg, must I open some preferences to do *that*?
Poor fool. Do you not realize that the programmers have an intellect so vastly superior to yours that attempting to use their creation without their help will most likely blow your feeble mind?
Phatose on 28/12/2010 at 22:04
Software developers assume end users will behave like idiots because end users always do so. Not only will they fail to follow basic instructions, but they will absolutely astound you with their creativity on how to screw up.
CCCToad on 29/12/2010 at 02:37
So taking the FOX approach and catering everything to the lowest common denominator is the way to go?
Seriously, though, the handholding can be annoying. One that I don't get is games that will constantly repeat tooltips, no matter how long you've played the game. If I'm near the end of the game, I probably already know which button will make my character take cover.
Minion21g on 29/12/2010 at 18:07
Quote Posted by the_grip
Some of these criticisms are actually paradigm breaking. The #1 problem to me is when there is a major paradigm shift in the way an applications is designed, but, while paradigms are legit, here's an example:
If the "File Type" is set to txt, then you should expect the file to be saved as txt. I assume this criticism is largely targeted at applications like Notepad... this type of application is expected to handle txt files first and foremost. I do think you should have some option to choose the default file type when saving documents, but I think it is perfectly reasonable to expect a .txt extension to be added *if* the application indicates it expects to save it as a txt file.
To be fair, .txt is a flatfile similarly to .cfg and .csv for that matter, and that flatfile association is what LS cares about I bet. Regardless, yeah, if its set for .txt you better well expect .txt as the output. Use Notepad++ to write up flatfiles instead. Really, with all things computer related, it's usually not the program. It's how the user uses the program.
My problem with software developers is that they can never agree on one set of standard syntax. For example, .txt in Windows ends each line with a carriage return then a line feed, whereas Unix is only the line feed. Why? What's the frigging point of making it different!?
Phatose on 29/12/2010 at 18:34
The point of making it different in that case is that it already is different. Neither Microsoft nor the zillion flavors of Unix are going to change it - and break compatibility throughout their system - for the sake of being in tune with the other guy. And changing over to a new, standardized format is the same amount of work as switching to the other layout would.
Fixing something like that means laying out a lot of resources for minimal gain.
d0om on 29/12/2010 at 23:40
And don't forget macs use just a CR.
Windows CR LF
Unix LF
Mac CR
With three different options, which one should change?
