SQLite3: No Room for Drama
calmlog.medium.com
SQLite3: No Room for Drama
1–10 of 18 posts
Re: SQLite3: No Room for Drama
#2I know we’re not supposed to whine about the medium but focus on the content. However, on Medium, the medium becomes the content because I can’t even read the damn thing without being accosted by some CTA popover. This is my quiet crusade against authoring on that platform.
Re: SQLite3: No Room for Drama
#3I know we’re not supposed to whine about the medium but focus on the content. However, on Medium, the medium becomes the content because I can’t even read the damn thing without being accosted by some CTA popover. This is my quiet crusade against authoring on that platform.
cough reader view cough
Re: SQLite3: No Room for Drama
#4feels like clickbait
Re: SQLite3: No Room for Drama
#5I know we’re not supposed to whine about the medium but focus on the content. However, on Medium, the medium becomes the content because I can’t even read the damn thing without being accosted by some CTA popover. This is my quiet crusade against authoring on that platform.
[deleted]
Re: SQLite3: No Room for Drama
#6is sqlite used for server side nowadays ? I've always thought this was highly not recommended.
Re: SQLite3: No Room for Drama
#7I love SQLite, but some arguments in the article seems contradicting each other.
1. Massive Max DB size vs It can't handle the traffic: If it can't handle the high throughput it doesn't matter how big it can get, because you never get there, you can't do 1 insert/sec and leverage 281 TB storage capability
2. It's just for small projects vs It can't handle the traffic: so it is for small projects, right? I know there are multitude of different types of applications, but when mentioned MySQL/PostgreSQL at the beginning of the article, I thought we would be talking about web/backend related applications.
SQLite has a different mental model, it wants to be simple and close to the code, hence you can't easily setup multi node replication
On the other hand, other databases want to manage your data in isolation, hence they're deployed on a separate machine and have out of box data replication/sharding mechanisms
Re: SQLite3: No Room for Drama
#8I know we’re not supposed to whine about the medium but focus on the content. However, on Medium, the medium becomes the content because I can’t even read the damn thing without being accosted by some CTA popover. This is my quiet crusade against authoring on that platform.
[deleted]
Re: SQLite3: No Room for Drama
#9I know we’re not supposed to whine about the medium but focus on the content. However, on Medium, the medium becomes the content because I can’t even read the damn thing without being accosted by some CTA popover. This is my quiet crusade against authoring on that platform.
Your quiet crusade should consist of refusing to read articles on Medium :(
Re: SQLite3: No Room for Drama
#10I know we’re not supposed to whine about the medium but focus on the content. However, on Medium, the medium becomes the content because I can’t even read the damn thing without being accosted by some CTA popover. This is my quiet crusade against authoring on that platform.
Your quiet crusade should consist of refusing to read articles on Medium :(
I did, every time it pops up, I go "I guess we're not reading that then" and close the article. It's not like I _need_ to know about some guy's opinions on SQLite3, it's just entertainment. It is optional.