Erik Naggum (1965 – 2009)
Lisp programmer.
They don't make poles long enough for me want to touch Microsoft products, and I don't want any mass-marketed game-playing device or Windows appliance near my desk or on my network. This is my workbench, dammit, it's not a pretty box to impress people with graphics and sounds. When I work at this system up to 12 hours a day, I'm profoundly uninterested in what user interface a novice user would prefer.
I may be biased, but I tend to find a much lower tendency among female programmers to be dishonest about their skills, and thus do not say they know C++ when they are smart enough to realize that that would be a lie for all but perhaps 5 people on this planet.
Note that ANSI standards also cost way too much compared to toilet paper, and they're pretty bad quality as toilet paper goes, too.
Some people are little more than herd animals, flocking together whenever the world becomes uncomfortable for any reason, seeking the comfort of those who agree with them, do not contradict them, and take care of their emotions. I am not one of those people. If I had a motto, it would probably be Herd thither, me hither.
Shed the idea that you were programming in an OO style. There is no such thing. You were only programming a particular object system. Now you get to program a different object system.
What I actually admire in Perl is its ability to provide a very successful abstraction of the horrible mess that is collectively called Unix.
Like so many other things in life, you rarely get only what you optimize for.
"Code sharing" is an economic surplus phenomenon. It works only when none of the people involved in it are in any form of need.
If the syntax is good enough for the information, it should be good enough for the meta-information.
Life is too long to be good at C++ – if you had spent all that time to become good at it, you would essentially have to work with it, too, to get back the costs, and that would just be some long, drawn-out torture.
Sufficiently advanced political correctness is indistinguishable from sarcasm.
The theory is the result of listening to the problem. When the theory acquires a life of its own because some people like it more than the real world, all kinds of uninspiring, uninteresting things happen, so the key is both to listen to the problem and to study the theory. But always remember that just as much theory is bunk as there are buggy solutions. There is nothing more wrong with "theory" than "solutions" – both their quality and their applicability are orthogonal to their existence.
Optimization is generally detrimental to future success, but it is the only way to accomplish present success in competition with others who are equally interested in short-term results.
The Novice has been the focus of an alarming amount of attention in the computer field. It is not just that the preferred user is unskilled, it is that the whole field in its application rewards novices and punishes experts. What you learn today will be useless a few years hence, so why bother to study and know anything well? I think this is the main reason for the IT winter we are now experiencing.
I have a cat, so I know that when she digs her very sharp claws into my chest or stomach it's really a sign of affection, but I don't see any reason for programming languages to show affection with pain.
If GML was an infant, SGML is the bright youngster who far exceeds expectations and made its parents too proud, but XML is the drug-addicted gang member who had committed his first murder before he had sex, which was rape.
A "new" language that differs from the rest of the crop by one or a couple features is proof positive that both what it came from and what it has become are mutations about to die. There are tens if not hundreds of thousands of such "languages" that people have invented over the years, for all sorts of weird purposes where they just could not use whatever language they were already using, could not extend it, and could not fathom how to modify its tools without making a whole new language. They never stopped to think about how horribly wasteful this is, they just went on to create yet another language called Dodo, the Titanic, Edsel, Kyoto-agreement …
C being what it is lacks support for multiple return values, so the notion that it is meaningful to pass pointers to memory objects into which any random function may write random values without having a clue where they point, has not been debunked as the sheer idiocy it really is.
Whoever decided to use the semicolon to end something should just be taken out and have his colon semified. (At least COBOL and SQL managed to use a period.)
I have actually programmed a fair bit in Perl, like I have C++ code published with my name on it. Other things I have tried and have no intention to do again if I can at all avoid it include smoking, getting drunk enough to puke and waste the whole next day with hang-over, breaking a leg in a violent car crash, getting mugged in New York City, or travel with Aeroflot.