Hacker News Reader

Except that it's a lie. Not accepting new feature requests is one thing, but what actually seems to be happening is that new code has been accepted into the master which then never sees the light of day.

Hiding behind "well we don't want to compromise the core software" after stringing other contributors along for years doesn't pass the sniff test.

Is there anything preventing you from running the latest version from git? Is there something special about a "release" that you're looking for? (I can think of several reasons why someone might want a release and not the latest master branch, but I'm curious about your specific reasons)

I am not OP, but think of it from a contributor's point of view: you work X hours on a new feature that even gets accepted into the master, but then you know that 99.9% of mosh users will not see it because it's not part of a release. I don't know how I would feel about that.

OMG amen to that! we have lost the notion of stability in the rise of agile software.

I completely agree with the sentiment!

I do wonder whether new releases are required to benefit from fixes and performance enhancements in libraries. Or is everything dynamically linked?