News for hackers. Stuff that matters.
[dead]
Re:What every programmer should know about memory (2007) by dboreham on Friday November 20, 2015 @01:00PM (#10602667)
I think it is very clear that he means the cited article. The post title should include the year (2007) since technology has changed somewhat in the 8 years since.
Re:What every programmer should know about memory (2007) by gugagore on Friday November 20, 2015 @05:26PM (#10604298)
I disagree with your judgement about the grammatically of the utterance. And if you've ever written comments about anything, for example, someone's writing or pictures, you'll probably say things like "me in Peru" or "needs revising" or "word is inappropriate"
Re:What every programmer should know about memory (2007) by xiaoma on Friday November 20, 2015 @10:06PM (#10605349)
I would never say, "word is inappropriate". I would say, "This word is inappropriate". It's clearer and there's almost no cost to using a well-formed sentence.

Similarly, I find comments where the single word "this" is used as an entire sentence detract from a forum based site. I can talk to u in allthememes! and sms abbreviations, but I chose to save that register for chat and look for something a bit more correct on forums. I readily admit that HN has been slowly trending away from that for nearly its entire existence.

Re:What every programmer should know about memory (2007) by gugagore on Monday November 30, 2015 @06:55PM (#10652771)
I was on the subway and saw "DON'T LEAN ON DOOR" and remembered this thread.

Your comment about "this" and internet shorthand and memes is not related to your grammaticality judgement, unless you are admitting to conflating "clarity" with "propriety".

Re:What every programmer should know about memory (2007) by dang on Friday November 20, 2015 @06:28PM (#10604568)
Please don't do this here. Blasting someone like that is rude at best, and outright mean when English is not their first language, as is the case with so many users here.
Re:What every programmer should know about memory (2007) by xiaoma on Friday November 20, 2015 @09:57PM (#10605326)
If there's anyone sensitive to the plight of a second language speaker, it's me. I can completely empathize with the struggle.

It probably wasn't the best way to phrase it and it's likely a losing battle anyway. I've found native speakers (which I believe the person I was responding to was) using this form more and more on boards such as this. Mistakes with uncountable vs plural distinctions are also increasingly common. E.g., "there's many reasons" instead of "there are many reasons".

As someone who spent years helping people with a variety of English problems including grammar, it's difficult to stop. I'll try to restrain this kind of comment to the articles themselves. There it's in the author's best interest to write in a way that doesn't cause the 30% or so of the population with stronger grammatical sensitivities to discount them.

Re:What every programmer should know about memory (2007) by gpvos on Friday November 20, 2015 @10:05PM (#10605348)
I am strongly grammatically sensitive. And although I am not a native English speaker, I claim that the sentence is grammatically correct. It's just a shortened sentence form. Which is often appropriate on forums and similar.
Re:What every programmer should know about memory (2007) by xiaoma on Friday November 20, 2015 @10:09PM (#10605359)
Hmm... I wouldn't have put the period between "form" and "which" in your comment either. Doing so made your last sentence a sentence fragment.

What's your native language? Your English appears to be at least very near native.

Re:What every programmer should know about memory (2007) by gpvos on Tuesday December 01, 2015 @10:35AM (#10656071)
Yes, I was aware of that.

Dutch, by the way.

Re:What every programmer should know about memory (2007) by dang on Friday November 20, 2015 @10:43PM (#10605449)
I'm in much the same boat as you, and I don't think it's necessary to stop; what's necessary is to err on the side of being helpful as opposed to judgmental or defensive.