1. 5
  1. 4

    Latest commit 13c8534 on Mar 14, 2011

    61 commits

    It’s dead, Jim.

    1. 2

      All that is gold does not glitter,
      Not all those who wander are lost;
      The old that is strong does not wither,
      Deep roots are not reached by the frost.

      (Edit to add: from The Fellowship of the Ring, J.R.R. Tolkien. Because every quotation is always new to somebody, and an unsourced quotation is the beginning of the end.)

      1. 2

        I’ve told off one person or another for “this isn’t updated, where are the new features” myself, software can be “finished” or be in “bugfix only mode”, I have no problem with that - but at some point even my threshold is crossed.

        The 61 commits tell me it probably wasn’t worked on extensively, even though it was at least a time span of nearly 2 years, with 4 individual committers. But nearly 9 years old plus this…

        1. 1

          I am in two or three minds about this.

          On the one hand (“in the one mind”?), you are completely correct that it’s probably not a very elaborate project, and nobody is actively developing it. (Leaving that recent fork aside, I’m not even sure it existed when you posted.)

          On the other hand / in the other mind, I don’t like the binaryness of the idea that a project is either good for building with or dead. There has to be something in any project that can further my understanding of the craft of programming? I guess my dislike of the idea that ‘dead (unmaintained) = not worth sharing’ was what prompted my previous comment. Not that you could get that from my comment, unless you’re a mind-reader. Although you guessed most of my objection, so perhaps you are?

          In my third mind, even if that Mercury project has something otherwise interesting in it – well, the submitter didn’t point it out, so practically the code’s interest is not going to be very accessible. Which makes my ‘it could be interesting even if it’s dead’ words high-minded but not backed up by praxis. (I did skim the code, and the codebase is small, commented, clear, nicely laid out, and nicely structured. So perhaps it’s of interest to folk thinking of building their own web framework in Lua?)

          1. 2

            As I said, I don’t like that mindset either, but 9 years is a long time, it at least would’ve warrented a (2011) tag. I’m not saying it’s historical, but if this was another language than Lua, it might as well have been historical and not even worth reviving.

            Also, and this is where was maybe too quick to judge, if this was something like a language ecosystem’s default lib/framework for anything, or doing something spectacular, it’s also a different story. But I’m not sure this website is the correct venue for submitting niche personal projects that are neither new nor noteworthy. (And not old enough to be historical).

            Although that may sound harsh, I don’t think I’d ever submit one of my own old (and dead?) projects and I’d be equally puzzled if someone else did. (OK, there is one, but I think it did some interesting things and the concepts were kinda new, so it wasn’t a port…)

            So yes, the answer was snarky and curt, but I didn’t flag it, just comment :P

            1. 1

              No worries, you were quite justified in saying what you did. My previous comment was more because I thought I ought to explain my own throwaway remark :-)

      2. 1
      3. 2

        Someone forked it earlier today and has made a few updates.

        1. 1

          Thanks for the hint. Wonder if it’s a coincidence? And why wasn’t the other repo posted then? :)

        2. 1

          What does this offer that Lapis doesn’t? Lapis is also sinatra like and more battle tested (itch.io for example).

          1. 1

            I tried to update my only Lapis project just two weeks ago and also didn’t have such a good impression. The old instructions with luarocks (discouraged by openresty) still kinda work, but iirc only with 1.6.0 and not 1.7.0 - but I might have just made some mistakes. (1.7.0 is from May 2018).

            I’m sure it’s still usable, but there are a ton of open issues and pull requests and I don’t have high hopes there will be a lot of maintenance…