3 ms·
This has to be a joke. If the Ruby implementation that saves the comment would simply contain the logic to save the static HTML file - the obvious implementati
by ckdot 4y ago
This has to be a joke.
If the Ruby implementation that saves the comment would simply contain the logic to save the static HTML file - the obvious implementation - no Postgres events are required.
- tracnar 4y agoHaving a database separates the view from the model. If you want to modify the generated HTML, it's much easier with the comments being separate from the HTML itself.
- ckdot 4y agoI don’t say to get rid of the database. Of course it makes sense to store the comments there. I say get rid of 1) the database events and 2) the Ruby logic to listen to these events. This can be done by the Ruby saving logic. It’s just over engineering to use events.