I'm sure you are pretty bitter about your project getting crapped on here, but it should have been a foregone conclusion. Someone, anyone, could have explained this position any time before you ran this thing all the way to the product stage and started announcing it. Whatever process you followed to get here appears to have been flawed; either you took too little advice, you took poor or unqualified advice, or you refused to accept valid criticisms.
If you want to wow this crowd with something as hackneyed as QR codes you're gonna have to do stuff that's on a different level[1]. Make that into a $10/month product bundled with all the bells and whistles of a mature marketing tracker and you might have something. I want to be clear that there's nothing wrong with what you have made, but the way you have positioned it to have more value than it actually offers. What you have today is the answer to a homework assignment, not a product, and it would be better received if you did not force it to wear a costume.
It's the ability to customize the codes that you're paying for. Ad logos, and an almost limitless amount of customization. If all you want is standard black and white squares, that's easy and free all over the place.
Adding logos to QR codes, changing colors or replacing squares with circles in QR code is a CS sophomore weekend project at best. It's really fun and quite easy to do. You don't even need to understand Reed-Solomon codes for that.
This project, however, doesn't even do it. It just imports popular react library `react-qrcode-logo` [1] which does all the job (few dozens lines, really) [2].
This is like telling someone in Marketing "recompiling the linux kernel and turning on some new drivers is really simple. You don't even need to understand kernel architecture to do that."
Yes, it's simple for you, but for folks who just want to make sure that all their QR Codes reflect their brand, having to recreate that every time isn't worth it.
I've actually been looking for a comprehensive and detailed comparison of Clickhouse vs Pinot, so this is timely for me. I like that this article has some easy to digest lists of what is supported in each implementation, but that's fairly high-level. The deeper dives into features and specific use cases was much more helpful.
