Some perspective on a destroyed career
rondam.blogspot.com
rondam.blogspot.com
I think it is much less important which language you use, than what you create with it. Otherwise you have a shed full of brilliant tools that have never been used.
I've noticed that the people who actually create things tend to be less dogmatic about languages.
People with too much GAS tend to be much like language weenies. They will go to absurd lengths to defend the "pure/fat/warm/etc. sound" of their favorites, an ultimately pointless endeavor considering that after a certain minimum of instrument quality, playstyle and post processing effects will both have far more impact.
To talk a little about myself, I'm a die hard libertarian, and I've spent countless hours being quietly angry about all the collectivists out there that wants to ruin our planet. Recently I've noticed though, that this rock-solid conviction of the superiority of a libertarian society isn't really productive for me in my relationships with others, and made it harder for me to intellectually appreciate good ideas from people who doesn't share my view.
I think the reason for this rigidity in my beliefs was that in my late teens, I felt as if I didn't belong anywhere, and getting an ideology to die for gave me a (false) sense of belonging.
I can't speak for this Lisp guy or the musicians but I can only assume that we perhaps share some similarities.
Meeting a person who wrote a masterpiece on the back of a deli menu would not surprise me. Meeting a person who wrote a masterpiece with a silver Cartier fountain pen on an antique writing table in an airy SoHo loft would SERIOUSLY surprise me."
i guess the same thing can be said for those who use aeron, multi monitor, big screens, etc
the true hacker will just shut up and code, even using crappy computer / resources
On the other hand, an aeron chair can be appreciably more comfortable than a cheap alternative, and multiple monitors can reduce the amount of friction a developer experiences (e.g., code in one window, documentation in another). While it's true that good people can make good with little, they can do better with more. If, of course, that "more" is something of actual productive value.
Some tools might reduce the "friction" but reduce functionality and usability in ways that you don't think of. As another example, I frequently see people creating huge hierarchies of folders in their home folders such as "/home/user/projects/school/year/class01/week_number/assignment_number/revision/". They think they're being organized, when really, they're just slowing themselves down. It makes it easier to classify things, but it makes it harder to actually get things done.
Multiple monitors is less effective on Linux. X can unmap, move, etc. windows without their permission, so virtual desktops still work when a program is being debugged (like when you need to look up documentation). Plus, emacs is pretty slim, visually, so you can often fit your program right next to it. 'Course, if you use eclipse, it sucks up extra space like VS.
(Vista might be able to move windows without their permission, since the contents are redirected to a buffer. I don't have vista to try.)
Actually, while some forms of the output may be functionally equivalent (it's hard to do good calligraphy with a ball-point), the experience isn't. (Some folks really enjoy using fine pens.)
It's unclear how the experience affects the output.
That said, the analogy made me smile. Perl really is one of those languages, that by learning, you only learn Perl. And maybe regular expressions, but I learned about those in theory of computation class. When I learned C I learned about the tenets of the OS: the call stack, virtual memory, system calls, interrupts, all the ugly stuff. Same with Java, it gave me good appreciation of OO, because it's so fundamentally OO. Basically, these languages were educational beyond themselves.
Perl, on the other hand, lets you get things done real fast in its problem domain. It also encourages some of the worst programming practices and an obsession with obscure brevity, code golf. More and more I'd just rather write everything in Python. Even though it may require 10 more lines of code, I can think about the problem in pretty much the same way I would in Perl. Plus, I can read the script afterwards, which really really helps.
A deep fryer is also super-utilitarian. Can you imagine McDonalds, or any burger chain, without fries? But it really is the nutritional equivalent of Perl.
Here's someone else who solves problems: http://blog.plover.com (and who wrote Higher Order Perl).
All learning is commendable, including learning from a language. But to think that knowledge comes only from existing languages is to constrain one's knowledge, and for oneself to be defined by one's tools. Languages aren't the source of intellectual nutrition; they are a conduit to it (or how could they be created in the first place?). The source is creating solutions to problems.
I wish my career were similarly "destroyed".
He implemented something at NASA, then wrote a paper about it.
(And oddly enough, I just realized he got his PhD from the same department I'm in.)
I think it is very hard to know more than two languages well, especially such different like western and eastern ones.
I have a dream, for example, to learn Japanese language, because I'm an anime fan, but I'm also realizing that this is almost impossible for me. Even my very weak English took several years of learning, because learning means practice, and this process is very slow. And if language is really difficult, like the Sanskrit it is impossible for sure.
So, when someone claims that he know some language, I assume that he should have at least 5 years of continuous practice, or it is just an empty claim.
I speak italian, portuguese, spanish, and english, and will be studying hindi later this year
It seems a bit dishonest to me.