quarnster

Feel free to maintain a fork and/or discussion forum yourself, I can put a link to it at the very top of the readme.

At one point it was written in javascript. Then in python. Then Go.

I still think a html frontend would be cool, and it's certainly my intent to keep as much of the code in the backend as possible to be able to swap one frontend with another.

It's not a pet project, I haven't written any real code for it for about 6 months.

My point (which perhaps you missed?) is that you don't get to tell me what I choose to spend my time on.

I don't care about what you need or don't need, maybe I enjoy writing code for the sake of writing code. Implementing the rope structure for example was fun, as was figuring out how to go about with the various ST3 compatibility tasks.

What I choose to do on my own spare time is none of your business no matter how much of a waste of time you think it is.

For this project in particular in its current state, I don't need people pointing out where it's broken. I know that it's broken and close to useless in fact and that there's a huge list of things to fix, implement or improve.

So if closing up the issues section gets rid of this unneeded negative reinforcement, that's a good thing and working exactly as intended.

If that actually happened, I'd be overjoyed, until then I'm not going to hold my breath.

In my experience with my other open sourced stuff on Github, others fixing stuff is very rare. Having issues enabled quickly turns into users demanding fixes and no amount of asking for others to chime in aiding with pull requests actually result in pull requests.

IIRC most pull requests come either out of the blue for something new no one has requested before, or they don't come at all until I explicitly say "I'm not going to fix this" and close the issue.

My contact info is not hard to find if you want to discuss a particular approach for a pull requests before implementing it.

One of the reasons it was retired is the same reason people can't open up issues on lime. Too much demand to fix everything that's broken, and not enough people actually fixing it combined with me not touching much C/C++ code personally.

I do still accept pull requests for it, and if anyone wants to step up as a maintainer I'd happily add them as collaborators after they've submitted a few pull requests.

Aha, so that's why there are 100's of new people starring it... ;)

Hello, thanks for the interest. I hope some of you will take the time to contribute in the form of pull requests.

I just updated README.md with a screenshot, here's a direct link: http://i.imgur.com/VIpmjau.png