3 ms·

Then there's no point in using javascript, go do something else No need to be rude. Look, I know JS likes to do things in ugly ways. It has great strength in t

by smosher 15y ago

Then there's no point in using javascript, go do something else No need to be rude. Look, I know JS likes to do things in ugly ways. It has great strength in the consistency of its syntax. That's cool. But by the time you say the word "just" you're being ignorant.

masklinn 15y ago
> No need to be rude. The statement was not intended to be rude and I'm sorry you took it this way, it was merely intended to be factual: you seem unhappy with javascript's core syntactic elements, you should use something else because they're not going to be changed. > Look, I know JS likes to do things in ugly ways. Uh... ok, whatever. > But by the time you say the word "just" you're being ignorant. Ignorant of what, of you trying to work around javascript's syntax in javascript for debatable reasons of personal aesthetics? No, I think I got that now, I was originally mistaken indeed in that I thought you were looking for an improvement to the language, not "fixing" an irrelevant syntactic pet peeve.
- smosher 15y ago
  The statement was not intended to be rude It comes off as a euphemism for much shorter phrase. Perhaps you didn't intend to be rude, but you failed to be polite. Ignorant of what (Exactly.) You've made assumptions and pinned them to me. I'd set you straight but I don't actually want to continue this conversation. Sorry it didn't work out.
  - masklinn 15y ago
    > Perhaps you didn't intend to be rude, but you failed to be polite. Considering your messages seem to be about misleading and avoiding spelling out your issues more than conversing, I had (and have) no reason to go out of my way to be polite. > I'd set you straight but I don't actually want to continue this conversation. And now you're plain and simply lying. You never intended to set anything straight (or you'd have done this in your previous comment instead of going for the pithy implication) and never intended this to be a discussion. > Sorry it didn't work out. It's not a relation, there's no "working out" to do.

by smosher 15y ago

masklinn 15y ago

> No need to be rude. The statement was not intended to be rude and I'm sorry you took it this way, it was merely intended to be factual: you seem unhappy with javascript's core syntactic elements, you should use something else because they're not going to be changed. > Look, I know JS likes to do things in ugly ways. Uh... ok, whatever. > But by the time you say the word "just" you're being ignorant. Ignorant of what, of you trying to work around javascript's syntax in javascript for debatable reasons of personal aesthetics? No, I think I got that now, I was originally mistaken indeed in that I thought you were looking for an improvement to the language, not "fixing" an irrelevant syntactic pet peeve.

smosher 15y ago
The statement was not intended to be rude It comes off as a euphemism for much shorter phrase. Perhaps you didn't intend to be rude, but you failed to be polite. Ignorant of what (Exactly.) You've made assumptions and pinned them to me. I'd set you straight but I don't actually want to continue this conversation. Sorry it didn't work out.
- masklinn 15y ago
  > Perhaps you didn't intend to be rude, but you failed to be polite. Considering your messages seem to be about misleading and avoiding spelling out your issues more than conversing, I had (and have) no reason to go out of my way to be polite. > I'd set you straight but I don't actually want to continue this conversation. And now you're plain and simply lying. You never intended to set anything straight (or you'd have done this in your previous comment instead of going for the pithy implication) and never intended this to be a discussion. > Sorry it didn't work out. It's not a relation, there's no "working out" to do.