I don't like many of SQLite's design choices, but the embedded use case at least makes many of them reasonable. MySQL has no excuse.
-
-
Replying to @sgrif
I heard a
@rorpodcast years ago about GitHub’s choice of MySQL. Know anyone over there who defends it?2 replies 0 retweets 0 likes -
Replying to @CodingItWrong
TBH if your team knows how to scale MySQL and has never scaled PG, that's a perfectly valid reason
1 reply 0 retweets 0 likes -
-
Replying to @CodingItWrong
It's a less compelling argument early on (even if your whole team knows MySQL better, but we're talking when your team is 3)
1 reply 0 retweets 0 likes -
Replying to @sgrif
I think the argument of that podcast ep was that PG was more bleeding edge and MySQL was more stable
2 replies 0 retweets 0 likes -
-
Replying to @sgrif
End of 2015! Ruby on Rails Podcast: 207: Choosing the Right Systems for the Job with Sam Lambert https://overcast.fm/+BlTra6DM0
3 replies 0 retweets 0 likes
Certainly MySQL is more stable (e.g. https://dev.mysql.com/doc/refman/5.5/en/mysql-escape-string.html … still exists b/c backwards compat)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
