"Hosting SQLite databases on Github Pages" is absolutely brilliant: it adds a virtual filesystem to SQLite-compiled-to-WebAssembly in order to fetch pages from the database using HTTP range requests phiresky.github.io/blog/2021/host…
Check out this demo: I run the SQL query "select country_code, long_name from wdi_country order by rowid desc limit 100" and it fetches just 54.2KB of new data (across 49 small HTTP requests) to return 100 results - from a statically hosted database file that's 668.8MB!
Looks like the core magic here is only around 300 lines of (devastatingly clever) code github.com/phiresky/sql.j…
phiresky points out that my "order by row id desc" demo is actually a worst case scenario - if you try the same thing without the desc it only takes 6 requests!
select country_code, long_name from wdi_country
order by rowid limit 100
What are the options for "serverless" PostgreSQL like these days? My definition of serverless here is that you don't have to spend any money at all if you're not getting any DB traffic, and cost then scales up as the traffic and storage you are using increases
Aurora PostgreSQL is the most obvious option, though it's not clear to me if you have to keep at least one instance running for it or if it fully "scales to zero" for projects that aren't receiving any traffic at all
Consensus in replies seems to be that this doesn't actually exist yet - scale-to-zero for a relational database server like PostgreSQL is evidently a whole lot harder than scale-to-zero for a stateless web application server as seen with things like Google Cloud Run
The feature I most want from Twitter is "view this user's tweets without showing their retweets"
Note that this isn't the same thing as turning off someone's retweets - I want to go to the profile of someone I don't even follow and see what they actually say, not just a stream of stuff they have retweeted
These days I'm so keen on having every commit link to an underlying issue thread that I'll sometimes write some code, then file an issue and close it with a commit a few seconds later
The real value here is having somewhere to continue the discussion around a change. I'll frequently add screenshots and links-to-documentation to an already closed issue. Also great to link to from release notes.
It almost becomes an out-of-band documentation and commentary thread - somewhere you can really dig into the reason for a change without fear of clogging up the code with comments that will inevitably become out-of-date in the future
github.com/bertrandmartel… by Bertrand Martel does all of the actual work, I just added a paper-thin wrapper around it that writes the resulting Pandas DataFrames out to a SQLite database