3 ms·
Not an objection at all sorry for not clarifying. I'm totally fine with older things and reposts, I was hoping to find out if there were updates that were, for
by codezero 10y ago
Not an objection at all sorry for not clarifying. I'm totally fine with older things and reposts, I was hoping to find out if there were updates that were, for example, not on this page, like a blog or Twitter.
I've enjoyed revisiting this project every time it's been posted to HN. Asking for updates shouldn't imply I'm somehow being contrarian but I know why you'd think so and wish HN would be more supportive in general. I'll do my best to be more clear in the future :)
- ci5er 10y agoYeah - everything on FB and Twitter is 2016 mid-May or so. A year ahead of the on-site blog, but not a heck of a lot of detail about what's going on. I wasn't trying to call you out for what I perceived to be an objection, but I see people say things like: "developer hasn't posted a commit for 9 whole months! no thank you! I'm out!". Which isn't very comment worthy; ranks right up there with "site doesn't display on my iphone". You weren't that direct (which should have been a clue that you were actually, you know, asking a real question), but you didn't seem very hostile, so I thought I would ask someone who was, you know, not hostile! :-) Because I seriously don't understand the objection when I see it and I've never taken time to ask.
- wmccullough 10y ago"I wasn't trying to call you out for what I perceived to be an objection" Except that you literally did...
- ZenoArrow 10y agoIt doesn't matter now, the question has been answered.
- codezero 10y agoI'm always happy to have these kinds of exchanges on HN :) To your earlier point where you mentioned github, I do think there is some reasonable doubt that people have for unmaintained repos. A maintained repo implies (pretty strongly) an active community. This is good for new and veteran developers. New developers are helped by good community and documentation, and veteran devs need the community when they hit a wall – using some library/framework to its limit, to the point that they need to make changes, or they think they need to make changes. Having an active community makes that process easier.
- ci5er 10y agoThat makes sense. I've never had much of an "active" community of anything -- just a lot of very demanding ticket (issue) submitters. Well, actually, maybe only 10% of the ticket submitters? They still irked me beyond reason. Maybe I need to grow a skin. Back in the bad old days of FTP, you could put up a gzipped tar file, and it worked for people, or it didn't. Maybe there was a mailing list, or even something on usenet. It seemed a lot more cordial and give-and-take, and less: "When are you going to support XYZ? I've been waiting for 3 whole weeks!" I just gave up on the new world and pulled the repositories. I guess you could say that I got off the damn kids' lawn! :-) Thanks!
- codezero 10y agoYep, I am similar to you I think – I've avoided doing much because supporting a community is hard and unless you have a really solid vision about what you will or will not do, incoming requests often seem overwhelming. I do think having a thick skin helps, as well as having distinct contributor guidelines. Trying to please everyone will always wear you down :)