You should put React library to your title, it makes it easier for potential users.
It should over time support all frontend libraries
Show HN: Clickvote – Open-source upvotes, likes, and reviews to any context
41–50 of 59 posts
Re: Show HN: Clickvote – Open-source upvotes, likes, and reviews to any context
#42congrats on learning some new tools! it is a bit 'astronaut architected' but you seem to have a history of building stuff and asking for feedback, that will always result in learning fast. hope you got some useful replies here!
a much simpler build system that's easy for people to adopt might have a higher chance of getting initial traction, and then you can add the layers only when they're needed. See YAGNI (You Ain't Gonna Need It) https://martinfowler.com/bliki/Yagni.html
Re: Show HN: Clickvote – Open-source upvotes, likes, and reviews to any context
#43Why do you need Kafka, Redis, Mongo, AND Postgres? Arguably it could all be done with Postgres or Redis: both have great pubsub implementations. But what could you possibly need two databases for and a queue implementation alongside a popular backend for queues? I don't mean to criticize, but the complexity of this is what I'd expect for something handling hundreds if not thousands of qps. Even then I'd expect you co…
Even better is to just use Clickhouse (maybe Kafka if there are lots of inserts and async_insert isn't sufficient) and Postgres.
Re: Show HN: Clickvote – Open-source upvotes, likes, and reviews to any context
#44Is the application architecture diagram a satire? It needs a lot more justification! Your documentation should very clearly explain why `upsert into user_rating (user_id, rating, thing_id)` doesn’t work at scale, and the limit where it breaks down. Maybe if you’re running a “upvotes SaaS” the architecture makes sense but the given architecture diagram is more complicated than the production product I work on ( https:…
I think you're absolutely right! What OP tries to bravely build here, does not need such a complex architecture, even if they want to turn it into a SaaS solution.
I also feel that your comment is slightly ironic, given the poor performance of Notion. I'm almost thinking (without having any clue about Notion's architecture) that Notion could benefit from a more complex architecture that prioritizes performance.
Re: Show HN: Clickvote – Open-source upvotes, likes, and reviews to any context
#45I’d love this for slack
Re: Show HN: Clickvote – Open-source upvotes, likes, and reviews to any context
#46Earlier quoted context omitted.
[flagged]
pg_dump --schema-only --table=tablename databasename
I have to say that this style of pointless tech flamewar is actually quite refreshing to encounter. It's like Slashdot in the old days Linux v BSD. Someone fires off a command or a patch that adds the functionality. Sort of nostalgic.
Ultimately, though, it would be nice to have a `.schema` equivalent in `psql` just as a convenience tool.
Re: Show HN: Clickvote – Open-source upvotes, likes, and reviews to any context
#47I’d love this for slack
Can't you just use certain reactions for voting in Slack?
Re: Show HN: Clickvote – Open-source upvotes, likes, and reviews to any context
#48congrats on learning some new tools! it is a bit 'astronaut architected' but you seem to have a history of building stuff and asking for feedback, that will always result in learning fast. hope you got some useful replies here! a much simpler build system that's easy for people to adopt might have a higher chance of getting initial traction, and then you can add the layers only when they're needed. See YAGNI (You Ain…
unless we all got click baited >
https://dev.to/nevodavid Technical Content Writing + DISTRIBUTION
Re: Show HN: Clickvote – Open-source upvotes, likes, and reviews to any context
#49Why do you need Kafka, Redis, Mongo, AND Postgres? Arguably it could all be done with Postgres or Redis: both have great pubsub implementations. But what could you possibly need two databases for and a queue implementation alongside a popular backend for queues? I don't mean to criticize, but the complexity of this is what I'd expect for something handling hundreds if not thousands of qps. Even then I'd expect you co…
Résumé Driven Development.
oh wow this is a term I’ve been looking for for ages!