Silent Bish: I fixed vsftp and the author didn't even say thank you

Silent Bish: I fixed vsftp: "Unfortunately, it's been a month, and there's been no response. He hasn't even looked at it."

This is the story of a guy spending way too much time on a pointless and fruitless cause: he fixed someone else's software - vsftp - for him, and sent in the fix to the owner, and didn't get a damned thing in response. No, really: the guy can't be fucking bothered to fucking mail him back a "yup, thanks" or anything.

So I looked at the link in the blog post, and I looked at the vsftp site. And I looked at some code, too. Holy crap is that program code ever fucking hard to read. The guy has routines that are nothing more than

routinea () {
 if (routined()) {
   routineb ();
 }
 else
 {
   routinec ();
 }

Okay. While it's all indented and pretty, it's also a plate of spaghetti. Everything is just a series of functions linked by various minor logic. It'd be pure hell to try and even remember what half of it is doing in any one coding session.

Insane.

After looking at this vsftp project, I'm really amazed that it's being used in place of anything else. The thing's going to be interesting when it's fully-developed, but the entire site and code is soft and squishy like the centre of a brownie that needs a bit more time in the oven.

I'll stay the hell away from this one for a year or two. Woe to the company who rolls this thing out as part of a paid product. With its hairy code and insanely crufty configuration file method, the code should be of dubious value until it's all cleaned out. A complete redesign may help.

Bah. Who'm I kidding? SuSE is probably shipping this thing already.