@Readlebee We tend to actively avoid MySQL because. Here are some of the reasons: https://gist.github.com/edwardloveall/5276a954140cee94b2d79e64db6936ff
@Readlebee I recognize that familiarity is important also and you're totally right to take that into account. On the other hand, this might be a good excuse to dive into a ⭐️ new thing ⭐️!
Either way, good luck and I'm excited to use Readlebee! 😀
@edwardloveall Thanks for that reference, it's really helpful! I do feel like Postgres is probably the "right" choice for this project. Plus knowing more than just MySQL will definitely be more enriching in the long run. 😁
Thanks! I hope I'm able to deliver something worth being excited for! 😅
@Readlebee Hah, extra "because" here. Too much editing 😬
It's true that familiarity is a plus, but is it really that different when you start a new project? I would imagine what will make most of the difference is the SQL, and that should be largely the same... except for the extra things you will be able to use in PG.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!