Hacker News Reader

Comment by tacos | Hacker News Reader

An obviously smart guy who doesn't know how to tell a story OR provide enough technical detail to the curious.

Who's the audience for this post?

Script programmers who never had to turn a computer off and on because they popped the wrong number of arguments off the stack before returning from a function?

Kernel hackers who didn't already see the checkins?

People who Google a problem after their kernel upgrade fails with obscure messages, who then receive no information on how to solve the problem?

Context is everything. From the title on down, this has none. If you're not going to take the time to do it right, let the commit messages tell the story.

I love learning about systems and I love a good "hunt down an obscure bug" story but this post offers neither.

View on HN

I thought it was interesting? It's not even like the author himself came here and put it in front of you. I can send you some links with much more comprehensive displays of vacuousness on the internet if you need some solid targets.

And it's not like the author has a comment section so I can tell him there.

Call me a dick if you like, but I'd love the web to contain a little middleground between mindless listicles and sentences like "Technically, the errors above come from ksh, when execve fails because there’s no room left in the new process to copyout argv."

I know what those words mean, I'm doubly-sure Ted does, and I'm sure it'd be a far better post if he spent another thirty words on the issue.

Call me a dick if you like, but I'd love the web to contain a little middleground between mindless listicles and sentences like...

And I'd love the web if people could provide criticism without overwhelming amounts of sarcasm and put downs. We can't always get what we want.

You're post easily could have said something along the lines of Interesting subject matter, but I would appreciate the article more if it either contained more technical details on the issue, or provided more context around the issue itself and it's implications.

Feel free to email him tedu@tedunangst.com or tweet @tedunangst

Just because there's a comment section doesn't mean you can't comment. You can read James Hague's thoughts on the matter here: http://prog21.dadgum.com/57.html

Or I can choose to leave a comment on HN and raise the broader issue of lack of context, something that plagues a lot of tech bloggers.

If the first words I see when I arrive on a site are "guest" and "flak," and then there's a misleading headline, and the seventh through ninth word in the post itself is "OpenBSD install kernels" with no further explanation as to what that is then I reserve the right to express both a local and global observation regarding the quality of the information as presented.

I'm amused that this is downvote central but turning a valid observation into a slightly lighter shade of beige isn't refuting my argument.

I originally read this article following a link from undeadly.org, the "OpenBSD journal", which provided enough context for me: http://undeadly.org/cgi?action=article&sid=20150209112628

I truly find this fascinating. That site has what appears to be a pokemon character wearing a drum kit, adds the line "Home: :Add Story: :Archives: :About: :Create Account: :Login:" and proceeds to quote the opening of the article while providing absolutely no additional information.

CmdrTaco used to provide a transitional sentence or two, and that's what made sites that look just like OpenBSD Journal actually have appeal and usefulness. Has the internet forgotten this lesson too?

Who's the audience for this post?

People who know who tedu is and interested in the type of things he tends to work on?

You know, every time I see the domain name I keep thinking it's Ted Nugent. Not even gonna lie.

I think this is more of the story of heartbleed that did not happen because it got caught during testing.

This bug doesn't have security implications. The term 'stack overflow' is slightly ambiguous, as it could either mean buffer overrun in the stack (which can often lead to arbitrary code execution) or the program simply running out of stack space (like in the article).

Reply on news.ycombinator.com