News for hackers. Stuff that matters.
Re:Linus vs C++, again by stcredzero on Thursday June 10, 2010 @04:28PM (#1421525)
That is a huge problem for communication. It immediately makes it much harder to describe things, because you have to give a much bigger context. It's one big reason why I detest things like overloading - not only can you not grep for things, but it makes it much harder to see what a snippet of code really does.

I think this is a limitation of our using flat text to program in. So long as our primary means of communication is linear speech and flat text, we will have this communications overhead. Collaborative systems that display the context to all concerned can overcome this. In fact, this is already happening! (Exercise for reader.)

Re:Linus vs C++, again by JustinSeriously on Thursday June 10, 2010 @05:01PM (#1421666)
I came here to quote that same piece, but for a different purpose. I am in complete agreement with him.

I think writing grep-friendly code is a good thing. I do my best to make all my Perl code easily grepped, it just makes debugging infinitely easier.

Re:Linus vs C++, again by protomyth on Thursday June 10, 2010 @05:24PM (#1421766)
Would a search tool other than grep change how you write code?
Re:Linus vs C++, again by JustinSeriously on Thursday June 10, 2010 @10:22PM (#1422531)
Probably not. I just said "grep" because it's such a basic standard, I really meant "easily searchable from a command line."
Re:Linus vs C++, again by stcredzero on Friday June 11, 2010 @08:10AM (#1423570)
What about a syntax-aware search? If this were as responsive as grep, wouldn't that be better? I think so. I use one in Smalltalk all the time.