What do you HATE in Computing?

and why?
I'll start,


C++, shit confusing language full of crap. dumb kids like it and do half arsed jobs of difficult tasks without understanding what they're doing with it. Dealing with C++ someone else wrote is fucking horrendus too.

Java hatred, Stop being a fucking idiot java is useful at times. Why is it still cool to hate java?

Python, ONE WORD, FORCED INDENTATION OF THE CODE, THREAD OVER.

This is already a language wars thread, jerk.

NOTHING WRONG WITH FORCED INDENTATION

>>2
>>3
Don't respond to me just say what you hate

))))))))))))))

>>5
lol

>>5
I agree.

Moore's law, I have a phobia it won't be satisfied.

Structure and Interpretation of Cudders in Python.

I hate:
- Digital Restrictions Malware, digital AIDS, software patents, imaginary property, region control, and all the digital terrorism coming from Microsoft, Sony, the mafiaa, and similar corporations. These corporations (as well as their bitch, the American government) are what I hate the most.

- ENTERPRISE. Business, management, TCO, synergy, solutions, multi-tier, Web 2.0, and all that bullshit. I abhor these moronic managers with their pointy hair, their suit and their business-speak, who take decisions and are in charge when they couldn't understand a fucking calculator. Projects take forever and fail, idiots write code, retarded platforms are used, and the result is an overpriced piece of enterprise shit.

- Java and similar enterprise bullshit made for mediocre programmers with a bloated ENTERPRISE object-oriented standard library, shoving their terrible object systems up your ass.

>>1
Java hatred, Stop being a fucking idiot java is useful at times.
Java is a terrible language with a toy object system and an insane ENTERPRISE standard library that will make you hate your life. Isn't this enough to hate it?

I hate JAVA. Useful my ass - its useful when I can wipe my ass with imports, JDKs, crappy IDEs, NullPointerExceptionNullPointerException
NullPointerExceptionNullPointerException
NullPointerExceptionNullPointerException
NullPointerExceptionNullPointerException
NullPointerExceptionNullPointerException
NullPointerExceptionNullPointerException
NullPointerExceptionNullPointerException
NullPointerExceptionNullPointerException
NullPointerExceptionNullPointerException
NullPointerExceptionNullPointerException
NullPointerExceptionNullPointerException
NullPointerExceptionNullPointerException
NullPointerExceptionNullPointerException
NullPointerExceptionNullPointerException
NullPointerExceptionNullPointerException
NullPointerExceptionNullPointerException
NullPointerExceptionNullPointerException
NullPointerExceptionNullPointerException
NullPointerExceptionNullPointerException
NullPointerExceptionNullPointerException
NullPointerExceptionNullPointerException
NullPointerExceptionNullPointerException
NullPointerExceptionNullPointerException
NullPointerExceptionNullPointerException
NullPointerExceptionNullPointerException
NullPointerExceptionNullPointerException
NullPointerExceptionNullPointerException
NullPointerExceptionNullPointerException
NullPointerExceptionNullPointerException
NullPointerExceptionNullPointerException
NullPointerExceptionNullPointerException

hello, fax. stop being a faggot and go away

people like >>10 hate it just because nobody likes their toy languages like lisp

>>11
I prefer "segmentation fault". It is obvious to an experienced programmer, but will stump a n00b for days.

>>14
I prefer "Traceback (most recent call last)".

notice all the java hate...
This is due to the posters being FAGGOTS

>>12
hello, Anonymous. stop being a faggot and go away

>>16
Hahaha, a Java programmer. I'm sorry for you.

Visual Basic.

Enough said.

I hate hate.

That recursive enough for you?

I hate people that hate hate

>>20
FUCK YOU

>>20
That's not actually recursive.

>>19

Classic Basic

10 PRINT "NUFF"
20 PRINT "SAID"
30 END

>>19
Don't say that, man. That brings back bad memories.

I used to have no internet access. No compilers. No assemblers. Not even a browser to execute javascript.
Just Microsoft Office and VBA ;_;

Abysmal user interfaces that is aided by the perpetuation of closed source programmers to not innovate. Go read the Humane Interface by Jef Raskin and you'll understand why computers are unnecessarily difficult to operate.

>>25
Ooh, that reminds me of something I hate!

Key chords that require a typing finger to produce. E.g. fuck keyboards with only a left ctrl key. Raskin, in his brain dead wisdom, thought that requiring a person to hold a key with their pinky while ACTUALLY TYPING WORDS is a lesser evil than a modal interface. Fucking nuts.

Leap keys sound pretty cool though, provided they are thumb operated. I wish there were a text editor I could try them out in.

>>26
The leap and the command quasimodes should be operated by the thumb. Other than the shift key, I don't really see any other pinky operated quasimode.

...

[quote]bbcode[/quote]

<blockquote>.<blockquote>

[blockquote]bbcode[/blockquote]

>>27
Well, Archy, the software his successors are making now, uses caps lock as the command key. Since he was alive when they picked that key, I can only conclude that he okayed it. I'm sure he knew it wasn't ideal, but he seriously underestimated what a bad idea it was, in my opinion. I'm still not sold on holding keys while typing at all either. Escape/enter as cancel/confirm are appealing to me. Pedals might be good.

Hey, since you seem to have read THI, is there any science in that book dealing with the advantages/disadvantages of modal and hold-it-down-the-entire-damn-time interfaces?

Are you SUAVE?
 Are you a SPACE TOAD?
 Are you a SUAVE SPACE TOAD?
 
 If you answered "Yes" to all of the above questions, then SICP (STRUCTURE AND INTERPRETATION OF COMPUTER PROGRAMS) might be exactly what you've been looking for!  Read SICP (STRUCTURE AND INTERPRETATION OF COMPUTER PROGRAMS) today, and enjoy all the benefits of being a satorized SICP reader.  SICP (STRUCTURE AND INTERPRETATION OF COMPUTER PROGRAMS) is the fastest-growing SMUG LISP WEENIE community with THOUSANDS of members all over the Internet! You, too, can be a part of SICP if you join today!  Why not? It's quick and easy - only 3 simple steps!
     * First, you have to obtain a copy of SICP and read it. You can read it online using your favorite web browser.
     * Second, you need to succeed in founding a Lisp-related meme in /prog/ on world4chan, a popular "programming for trolls" website.
     * Third, you need to join the official SICP home /prog/ on world4chan, and apply for membership.
 Talk to one of the satorized overlords or any of the other members in the board to sign up today! Upon submitting your application, you will be required to submit links to your successful meme, and you will be tested on your knowledge of STRUCTURE AND INTERPRETATION OF COMPUTER PROGRAMS.  If you are having trouble locating /prog/, the official STRUCTURE AND INTERPRETATION OF COMPUTER PROGRAMS board, you might be on a wrong web sight. The correct address is http://dis.4chan.org/prog/. Follow this link if you are using a http client such as telnet.  If you have Sussman points and would like to support SICP, please don't sage this post.

                        //`'''```,
              o        //SICP   `.,
        ,....OOo.   .c;.',,,.'``.,,.`
     .'      ____.,'.//
    / _____  \___/.'
   | / ||  \\---\|
   ||  ||   \\  ||
   co  co    co co

is there any science in that book dealing with the advantages/disadvantages of modal and hold-it-down-the-entire-damn-time interfaces?

Hell yes. It's been experimentally proven that sustaining an action WILL NOT be forgotten by the operator. The benefit of this technique is that the user doesn't have to remember the current state of the application when invoking a command. The same action WILL ALWAYS produce the same perceived result.

In general usage, modal interfaces should only be used for setting configurations that don't change very often. Examples would be for a light switch, or setting an airplane's throttle value or cruising along a highway on cruise control.

For situations where an object state is changed more often, hold-it-down-the-entire-damn-time interfaces (aka. quasimodes) are far superior. You wouldn't want to drive your car in the city or around the town in cruise control. There are so many examples on the computer for unnecessary modality. One would be saving files - there shouldn't be any need to save files these days as the computer should do it automatically.

>>34
I understand that it will not be forgotten, but what are the detrimental effects of having a command line that needs to be expressly confirmed or dismissed? They do not seem huge to me. I may not use cruise control on city streets, but I sure don't want to hold my shifter in the proper gear either. In the case of a command line, how the hell am I going to forget that I'm in the middle of typing a command?

While I can accept the argument for large numbers of modes and for modes you could easily forget you're in, it sounds an awful lot to me like he's taken anti-modality to the point of zealotry. Is there any science specifically on the subject of command lines that will be typed in the space of a few seconds then explicitly confirmed/denied?

>>36
I hate whatever this guy doesn't.

>>35
1. References to the science behind modality is in the book. Read it and be greatly enlightened. It's the SICP of interface design ;)
2. People only have one locus of attention. An interface is non modal if the interface is the user's locus of attention. The more modes you have to keep track of, the harder it is to do your job.
3. A car's speed is within the user's locus of attention and the current gear of the car should also be within the user's locus of attention so therefore, the car's gearing system shouldn't be modal. The command you're typing should be the locus of attention and therefore, the command line shouldn't be modal if it is your locus of attention.
3. He's 'anti-modal' because he understands the negative connotations that occurs with bad interface design. Modal interfaces contribute to bad interface design. Bad interface design wastes time, effort and mental power. Bad interfaces can also lead to physical harm and death; think of commercial plane pilots and how much information they have to deal with.

Is there any science specifically on the subject of command lines that will be typed in the space of a few seconds then explicitly confirmed/denied?
I don't really understand what you're asking. I'm guessing you want to know about GOMS http://en.wikipedia.org/wiki/GOMS. I am also guessing you want to know about the study of Human Computer Interaction http://en.wikipedia.org/wiki/Human_computer_interaction

>>37
You look like you know what you're talking about. Can you give any advice for books to read?

I've read the Design of Everyday Things and About Face, and I plan to read The Human Interface and then Don't Make Me Think. Are there any critical ones I'm missing?

>>36
Ahh, a properly recursive post.

>>37
I've been planning to read it. I hear it's got science, but I'm wondering if there is any on this specific topic (or something else that applies without a lot of assumptions). The question in my mind is whether people make fewer entry errors with a quasimodal command line than with a modal line. Ideally I'd like to see something like the following: an experiment in which subjects enter commands on an Enso (the proper name for the program I mentioned earlier -- I was thinking of their older effort) style command line and on a command line that has a key to summon it and requires either a key press to confirm or cancel. Subjects would go down a list of words and enter them into the command line. From this I would like to see error rates (number of aborted or mistyped words), time taken to input the words, and a survey taken at the end asking each subject how they felt about the input style. This would be very interesting in the event that there was no clear difference in efficiency between the two systems, and somewhat interesting otherwise.

My worry is that his approach to this particular interaction task is a little too theoretical, and not enough practical. So I'm asking now, to satisfy my curiosity until I have a copy in my hands, whether the book sciences on this task or something very similar.

>>39
Further investigations would involve subjects operating a summonable command line to accomplish a list of tasks, which would provide insight into the differences between using a command line without thinking (copying a list) and while thinking.

Maybe I'll do it myself sometime, along with retesting and expanding on Bruce Tognazzini's mouse vs. keyboard character replacement task. I'd throw in leap keys too.