Update hogan.js to track the latest Mustache spec, close remaining bugs, and make it clear the project is in maintenance mode

[sayrer]

I was alerted to mustache/spec#125, which covers most of the non-standard features shared by Mustache.java and hogan.js. It's been ~8 years since I seriously worked on this project, but this seems like a good time to close things up.

After this work is done, I'll add a note to the README that makes it clear the project is not adding new features, and is in maintenance mode. Serious bugs, such as security issues, will be addressed. New features and performance work can be done in a fork.

[jgonggrijp]

I'm working on a new Mustache implementation for JavaScript that I hope might become a worthy successor of hogan.js.

[willnorris]

@sayrer let me know when you've finished up that final work, and I can formally archive this repo. If there are other projects (like the one @jgonggrijp describes) that we should point people toward, we can certainly do that as well.

[willnorris]

@sayrer and thank you by the way for being willing to do that final cleanup, even after all these years! :)

[willnorris]

@sayrer: is this still something you're interested in doing, or should we just go ahead and archive as-is? (Either is fine, of course... I appreciate you even being willing to continue this work)

[jgonggrijp]

@willnorris I appreciate your willingness to point people to other projects, like mine. I haven't published mine yet. Would it be OK for you to wait with archiving until I have done that, and if so, for how long?

[willnorris]

I don't have a set timeline, necessarily. Though I think we may also just link to https://github.com/topics/hoganjs for example (there's nothing there now), and any related projects can add that topic even after we archive the repo.

[jgonggrijp]

That's a clever solution! My project is on GitLab, though, so it remains to be seen whether I'll be allowed to add it to GitHub's topic (technically it's possible by editing the topic Markdown and submitting a PR, but they might reject the PR for promoting a competing platform).

My library is in working order (it builds, it performs well and it passes all the specs), but I still need to write the documentation. I'm currently occupied with other things so it will likely take a couple of months before I publish. If you want to archive Hogan before that time, maybe you can just mention that I have something coming up and point people to my GitLab profile (https://gitlab.com/jgonggrijp) or my Twitter (https://twitter.com/juliangonggrijp). Besides suggesting that people keep an eye at the hoganjs topic, of course. I would be grateful for that.

[sayrer]

@sayrer: is this still something you're interested in doing, or should we just go ahead and archive as-is?

Still interested--sometimes life gets in the way. I should have some spare time in the next few weeks, though. I only noticed this because I was over in #274 evaluating the claims there.

[jgonggrijp]

@willnorris @sayrer I just made my implementation open source. It's called "Wontache". Home page in case you want to link to it: https://jgonggrijp.gitlab.io/wontache/.

I'm not ready to attract a lot of attention just yet, but at least it is presentable enough that it doesn't have to be hidden anymore.