News for hackers. Stuff that matters.
Re:Our web development workflow is completely broken by ritchiea on Wednesday June 26, 2013 @02:31AM (#5944483)
And once again the top comment doesn't do anything to continue the thoughtful discussion that began in the article, instead providing a pedantic correction.
Re:Our web development workflow is completely broken by lmm on Wednesday June 26, 2013 @06:13AM (#5945126)
And once again the top reply to the top comment has even less value, sending us off into pointless meta-discussion.
Re:Our web development workflow is completely broken by RyanMcGreal on Wednesday June 26, 2013 @07:49AM (#5945395)
Pike: That's a technicality.

Spock: I am Vulcan, sir. We embrace technicalities.

Re:Our web development workflow is completely broken by gadders on Wednesday June 26, 2013 @04:33AM (#5944802)
It's not the most important comment on the subject, but it is right that the firebug developer get credit.
Re:Our web development workflow is completely broken by foobarbazqux on Wednesday June 26, 2013 @02:48AM (#5944541)
If it weren't for pedants, we wouldn't have computers.
Re:Our web development workflow is completely broken by tinco on Wednesday June 26, 2013 @02:58AM (#5944560)
Yes, because the introduction of the computer was a minor change to the world that only a pedant would have bothered with?
Re:Our web development workflow is completely broken by foobarbazqux on Wednesday June 26, 2013 @03:23AM (#5944624)
Good point, it wasn't a minor change. I meant to specify working computers.
Re:Our web development workflow is completely broken by philh on Wednesday June 26, 2013 @03:59AM (#5944725)
That doesn't seem relevant. If it wasn't for hunter-gatherers, we wouldn't have much of anything; but that doesn't mean hunter-gatherers have much to contribute to particle physics.

There are times when it's important to be pedantic, like when you're writing software. (I don't think we normally use the word "pedantic" in these cases, but I'm not going to argue the matter.) And there are times when it's not important, like when an article mixes up the order in which two pieces of software were released.

Re:Our web development workflow is completely broken by foobarbazqux on Wednesday June 26, 2013 @04:57AM (#5944888)
A cornerstone of writing any kind of history is establishing an accurate chronology of events. In peer-reviewed articles the details of who came first in related work sections are critical. At any rate, I think many of us simply find it interesting to hear the real story. It's not like the guy was correcting a grammatical mistake, and it's not like he was impolite about it.
Re:Our web development workflow is completely broken by aptwebapps on Wednesday June 26, 2013 @08:13AM (#5945483)
There's nothing wrong with the comment in and of its self, in my opinion. In fact, I appreciate it. But it's too bad that relevance to the original article seems to have so little correlation with votes.
Re:Our web development workflow is completely broken by counterpointer on Wednesday June 26, 2013 @06:44AM (#5945218)
This would be much less of a problem if we could collapse comment trees like on Reddit. It would be just easy to minimize and ignore. I think someone made an extension for that.
Re:Our web development workflow is completely broken by balac on Wednesday June 26, 2013 @09:02AM (#5945704)
You might find the Hacker News Collapse extension useful: https://chrome.google.com/webstore/detail/hacker-news-collap...