I expected to learn something from it - especially when it's popped on the front page of HN. Am I expecting too much of HN?
My train of thought when I saw the link "a key-value store": what data-structure are they using? A hashmap? How are they resolving conflicts? Is it in memory? How are they persisting data? Do they support multiple instances? What about concurrency? etc.
Of course I might be a bit disappointed when the project is just 4 web APIs on top of sqlite table.
If it makes no sense, ask a question or ignore it if it's not interesting. But you can't just one-liner shit on other people's Show HN, whatever you expect.
It's not HN job to entertain you. Someone wrote some software they thought was useful, so they are sharing it. If you don't like it down vote and move on. Get off your high horse.
That's a bit harsh, while I don't agree with OP I don't think that your language helps in promoting a healthy discussion about what is reasonable to expect from a HN front-page post.
Also you say that "it's not HN job to entertain you". What is HN's job then? Because honestly I do come here to read things that entertain me.
Fair enough. I did share some of those expectations too tbh and it was indeed surprising that the solution was that simple. But to be fair it does not promise any of that and it does what it sets out to.
My train of thought when I saw the link "a key-value store": what data-structure are they using? A hashmap? How are they resolving conflicts? Is it in memory? How are they persisting data? Do they support multiple instances? What about concurrency? etc.
Of course I might be a bit disappointed when the project is just 4 web APIs on top of sqlite table.