Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

SQLite3: No Room for Drama

calmlog.medium.com

Post reply on HN
Print view View original

11–18 of 18 posts

Re: SQLite3: No Room for Drama

#11

Post by bananapub »

toxik wrote: post #2

I 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.

it is very very funny that Medium was initially a breathe of fresh air amongst the shitty, ad-ridden layouts of then-popular blogging sites, and has now deliberately made themselves unusable in turn.

Re: SQLite3: No Room for Drama

#12

Post by bananapub »

I feel a bit bad if it's a human, but I can't even tell if this sort of vapid, uninteresting article was written by an LLM or just someone who is not good at writing and doesn't know much about the topic.

either way though, obviously humans should do whatever writing they but aggregators like HN should reject ones like this.

Re: SQLite3: No Room for Drama

#15

Post by threatofrain »

toxik wrote: post #2

I 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.

Yup and authors are supposed to fit their content on a platform that never cared to equip them with tables, charts, or other forms of technical display. Even markdown on Github is way better for technical authoring.

Re: SQLite3: No Room for Drama

#16

Post by threatofrain »

tuyguntn wrote: post #7

I 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…

My problem with SQLite is that I've been using it as a quick and dirty up-and-going weapon with easy backup solution, but even for small projects I find myself going multi-service or multi-node on accident. Really too easily.

I'm starting to think of using PSQL as my dirty up-and-going weapon.

Re: SQLite3: No Room for Drama

#17

Post by bsaul »

chungy wrote: post #13
bsaul wrote: post #6

is sqlite used for server side nowadays ? I've always thought this was highly not recommended.

It has been for 25 years. If it solves a problem well, feel free to use it.

in which setup ? I don't think of a regular stack where you'd want a db stored as a file local to your api server. Can you store that sqlite file on a persistant ebs volume ?
Post reply on HN