News for hackers. Stuff that matters.
Re:Why Apple's 3.3.1 is great for hackers and (smart) founders. by volida on Thursday April 15, 2010 @06:11AM (#1267443)
The part you have in quotes is really wrong because he is not saying something like that. Why are you changing what he said? This is really irritating. People use quotes when they want to refer to a statement as it was made.

which is "technical resources to tell whether an executable has been compiled from human-written C code or compile-target C code"

Re:Why Apple's 3.3.1 is great for hackers and (smart) founders. by jacquesm on Thursday April 15, 2010 @06:50AM (#1267489)
> People use quotes when they want to refer to a statement as it was made.

Apologies, you're right. That was not the intention of the quoted bit, it was meant as a statement of what this piece makes me feel like. If I 'quote' a statement online I use the > mark (like above), I don't know of a typographical convention that would convey what I tried to do here other than using quotes.

Suggestions ?

Re:Why Apple's 3.3.1 is great for hackers and (smart) founders. by volida on Thursday April 15, 2010 @07:04AM (#1267505)
The thing is that most of the times, people read comments and then the article. So, I think it would be best if you are going to comment on a certain aspect to just include the original peace and then comment on it.

Other than that I am not aware of a more conventional way.

Re:Why Apple's 3.3.1 is great for hackers and (smart) founders. by WildUtah on Thursday April 15, 2010 @10:49AM (#1267927)
Single 'scare quotes' in English can provide the needed signal to the reader that you are using a paraphrase or exaggerated characterization of a position.
Re:Why Apple's 3.3.1 is great for hackers and (smart) founders. by jacquesm on Thursday April 15, 2010 @06:43PM (#1269157)
Thanks! I never realized there was such a big difference in which style quotes you use.