Why I call myself a Javascript Programmer

Re:Why I call myself a Javascript Programmer by amalcon on Monday October 25, 2010 @04:31PM (#1831478)

Except that C is not like wood, in the sense that it's a substrate out of which programs are constructed. It's more of a notation for describing the program, which the compiler then translates into another description, which the hardware then "runs" without the program ever being brought into existence as such. Therefore, C is more like a specific type of blueprint: it's good for building sheds, but it's not good for building motors or skyscrapers.

It's not like a blueprint, either, because you can just go ahead and build a birdhouse with no blueprint, but you can't just go ahead and build a program with no language.

We can pick holes in one metaphor after another, and fundamentally get nowhere. The point is simply to not over-specialize on any one environment, unless either you strongly believe it's the best one for every job or you're pretty sure you'll only ever want to do that job. I would contend that most people know neither of those things with any real certainty.

[ Parent | on HN ]

Re:Why I call myself a Javascript Programmer by raganwald on Monday October 25, 2010 @04:39PM (#1831504)

I think your argument is extremely literal. Metaphors don't sugest that X is Y or that X is like Y in every way, just that from a certain perspective, X has a lot in common with Y. So there will always be holes to pick in every metaphor.

Your argument reminds me of another Perlisism:

There will always be things we wish to say in our programs that in all known languages can only be said poorly.

http://www.cs.yale.edu/homes/perlis-alan/quotes.html

[ Parent | on HN ]

Re:Why I call myself a Javascript Programmer by amalcon on Monday October 25, 2010 @05:03PM (#1831580)

It's true, and that's sort of the point. My "argument" (as it was firmly tongue-in-cheek) was more literal than yours, just as yours was more literal than the hammer argument. The whole idea was to demonstrate that there's always a more apt metaphor. When you get to the point where you can't find a difference, it's not really a metaphor anymore.

The best part about metaphors is not the conclusions one can draw from the similarities between two things. It's the conclusions one can draw from the differences.

Also. for what it's worth, I think that quote applies just as well to human languages as to programming languages. Perhaps the metaphor itself might make a good metaphor for programming? :)

[ Parent | on HN ]

Re:Why I call myself a Javascript Programmer by tjogin on Tuesday October 26, 2010 @01:34AM (#1833158)

I don't see the harm in specializing, really. There are plenty of room, and need, for both generalists and specialists. Being a specialist doesn't mean you are unable to learn new things, or that you are daft.

I think what people really mean is "don't be daft".

[ Parent | on HN ]