3 ms·
Added in edit: Seeing that this is getting down-votes suggests either that I've not been sufficiently clear in the point I'm trying to make, or that you think I
by ColinWright 12y ago
Added in edit: Seeing that this is getting down-votes suggests either that I've not been sufficiently clear in the point I'm trying to make, or that you think I've phrased it in an unacceptable way. Either way, sorry you don't think this fits here, but I'll leave it for others to down-vote, correct, reply to, or support, as they see fit.
Another edit: Getting more down-votes, but not learning anything. Do you think this is the wrong place to say this? Or do you think I'm just wrong to worry about this level of precision in "normal" speech? Reply! Engage! Tell me why I'm wrong.
========
I'm going to be "that guy" ... warning: Rant ahead.
The wording of this question is like sandpaper on my brain - for me, the "only" is misplaced. Assuming he is asking:
What is there that I can do in Erlang,
but cannot do (or is significantly more
difficult to do) in other languages?
With that reading, I feel the question should be:
What can I do only in Erlang?
The question as phrased, to me, admits the alternate interpretation of:
What does Erlang force me to do?
English, and natural languages in general, are weird things. To quote the great Terry Pratchett:
It's very hard to talk quantum using a language
originally designed to tell other monkeys where
the ripe fruit is. -- (Night Watch, 2002)
I'm sure I've seen it before, but Google searches are just turning up places where I've re-quoted it, but:
When using plain language is it difficult
to construct a sentence that a determined
adversary cannot misconstrue.
You may argue that in this case it doesn't matter, but I would suggest that practising precision in language is important, and helps to avoid sloppy thinking.
This comment is intended to be constructive, although I admit freely that it is off-topic for the submission. Even so, I think it's useful to think about these things. I wonder if Erlang makes it easier to be truly precise about something.
- davidw 12y agoThat's actually the first thing the answer in the post addresses: > Anything can be done in any language, so the technical answer is "nothing". But the spirit of the question begs for an answer, especially in a company situation with deadlines.
- ColinWright 12y agoI read that first answer (and the others) carefully before writing the above, and I don't think it does. Well, let me be more precise. The answer addresses the question I think the questioner intended to ask. What the answer does not do is fully disambiguate the question as asked, nor does it even point out that the question as asked is ambiguous. It just takes what it thinks is the most obvious interpretation, and answers that. Which is fair enough. Most people are going to adopt that interpretation and understand the intent of the question. That's not addressing the point I'm trying to make, which is that the question as asked is ambiguous, and yet a simple re-wording would not be ambiguous. Or at least, not as ambiguous. But I guess my point is lost, and people will down-vote this thinking I'm just picking nits. Lost cause, but I honestly don't understand why programmers of all people should care so little about the careful and precise use of natural language. They appear not to, and I'll have to take that as an axiom without understanding. To be honest, your reply has made me stop completely and reassess everything. In particular, the fact that you of all people seem not have missed completely my intended point makes it perfectly clear to me that I quite simply have failed utterly to make my point at all. I know your posts and comments on HN, I recognize your nick, so to have you not see the point means that, somehow, it's simply not there to be seen. I'll have to go away and think again as to whether it is in fact possible to make the point, and if possible, whether I'm a good enough writer to do so. Current evidence suggests not. And finally, you say ... That's actually the first thing the answer in the post addresses ... Maybe I've mis-interpreted your use of "that's", and perhaps I don't know which part of what I've written you think is being addressed in that first answer. Perhaps we're just talking past each other.
- davidw 12y ago> Perhaps we're just talking past each other. Probably. I think most of us saw the title and reacted like the guy posting "well, technically, nothing" and moved on to the however, which is a fairly straightforward list of "what are the things this system is the best at", which is mostly what we're interested in as programmers and/or startup people. I didn't downvote you, of course, since people can't downvote stuff on articles they have posted.
- 12y ago
- triangleman 12y ago"Only" is an adverb in this case, and can be placed anywhere in the sentence for stylistic reasons. In all spoken language (as well as computer language), context is king, so we all knew what the title meant, your sandpaper notwithstanding. If the author was trying to ask "What does Erlang force me to do?" then he would have written that.
- ColinWright 12y agoThank you for your reply - it's very useful to me to see the viewpoints of others. It's becoming clearer all the time that my use of and views on language are very much in the minority. However, to respond ... > "Only" is an adverb in this case, > and can be placed anywhere in the > sentence for stylistic reasons. That doesn't seem right to me. Only what can I do in Erlang? What can only I do in Erlang? What can I only do in Erlang? What can I do only in Erlang? What can I do in only Erlang? These, to me, mean different things. > we all knew what the title meant, > your sandpaper notwithstanding. This is a case of "plausible interpretation" and I agree completely that of the different interpretations, probably only one of them really made sense given the context. It is still the case that I had to re-read to make sure something else wasn't meant, and I find it hard to believe that I'm unique. But what I take away from your comment is that, in your opinion, we should just go with the most plausible interpretation we can think of, and not worry too much about being too precise. You are clearly in the (possibly overwhelming) majority.
- triangleman 12y agoOK, maybe "anywhere in the sentence" goes too far. But the need for style in writing is super-important. If I was telling you about how to beat the 2nd level of Legend of Zelda, I might say You can only get to the final boss by taking the door on the right. Or I might say You can get to the final boss only by taking the door on the right. Which phrase has more impact in your opinion? Also note that in neither of these cases am I implying You can only take the door on the right.
- ColinWright 12y ago
- dragonwriter 12y agoIn generally, I think the kind of point you are making here is valid (and reflects an important source of miscommunication in the real world which is especially frequently an issue because imprecise expressions get extracted from their root context which might illuminate the intent that differs from the wording -- this is common when requirements discussions and informal written exchanges get reduced to requirements documents, for instance, and also, as here, when headlines get presented in aggregators out of their original context [though, in a sense, headlines are designed to be viewed without benefit of context, and have a particular need to be clear without context for that reason.]) OTOH, the actual phrasing here, while awkward, doesn't, to me, present the interpretation you offer of "What does Erlang force me to do?" -- indeed, there's no simple way of keeping the basic structure and moving "only" in that sentence to get that meaning (the closest sentence I can see which can communicate that meaning is "What is/are the only thing/things I can do in Erlang?") That's not to say its not both awkward and ambiguous -- "What can I only do in Erlang?" -- even absent context -- is hard for me to read as anything other than an awkward phrasing of either "What can only I do in Erlang?" or "What can I do only in Erlang?", the latter of which is apparently the intended meaning, the former of which asks about the authors unique strengths in Erlang that aren't equalled by any other programmer.