> Audio quality is decent here too. Listening to "Fast Car" now, and the quality is solid. :)
Fast Car was terrific, thanks for sharing! It is especially amazing considering this recording was made in 1988, just one month and one day (how poetic!) after Fast Car was released as a single.
"Talkin' Bout A Revolution" is in there as well, and some stuff marked as "unreleased".
The entire Tracy Chapman recording there is actually really well put together. The volunteers who did the work to transfer it from cassette and clean it up, did an outstanding job on this one.
SQLite has a ".backup" command that you should always use to backup a SQLite DB. You're risking data loss/corruption using "cp" to backup your database as prescribed in the article.
Related, there is also sqlite3_rsync that lets you copy a live database to another (optionally) live database, where either can be on the network, accessed via ssh. A snapshot of the origin is used so writes can continue happening while the sqlite3_rsync is running. Only the differences are copied. The documentation is thorough:
Yeah, using cp to backup sqlite is a very bad idea. And yet, unless you know this, this is what Claude etc will implement for you. Every friggin' time.
Well, humans also default to 'cp' until they learn the better pattern or find out their backup is missing data.
Also, my n=1 is that I told Claude to create a `make backup` task and it used .backup.
I don't understand the double standard though. Why do we pretend us humans are immaculate in these AI convos? If you had the prescience to be the guy who looked up how to properly back up an sqlite db, you'd have the prescience to get Claude to read docs. It's the same corner cut.
There's this weird contradiction where we both expect and don't expect AI to do anything well. We expect it to yolo the correct solution without docs since that's what we tried to make it do. And if it makes the error a human would make without docs, of course it did, it's just AI. Or, it shouldn't have to read docs, it's AI.
The web is the only major platform that has a language monoculture to its detriment (i.e., not all problems are Javascript shaped). IMO the web ought to become multilingual (and become JS optional_ to further ensure its continued longevity and agility. Hopefully one day browser vendors will offer multiple runtime downloads (or something similar capability).
WASM already offers this, for better or worse... There should be improved interop APIs for DOM access, but WASM is already very useful and even for directed UI control, "fast enough" a lot of the time. Dioxus, Yew and Leptos are already showing a lot of this to be good enough. That said, I would like to see a richer component ecosystem.
All the embedded systems I've worked in have many languages you can use to compile whatever, burn, and run whatever you like. Consoles run game engines and programs written in all sorts of different languages. They don't care as long as they can execute the binary. Phones can run apps using many different languages (C, C++, Rust, Python, etc.).
It is very disappointing that these new type checkers don't support plug-ins, so things like django-stubs aren't possible. That means you're stuck with whatever is delivered with these new type checkers. It must be really difficult since none of them support plug-ins. Some of these newer type checkers promise support for Django, but you're stuck with what they (will) have on offer. Also, you'll likely want typing for other libs you might use.
You're comparing apples, bananas, and pineapples while pretending they're all one thing. Switchblades are extremely effective (albeit expensive) anti-personnel (300 model) and anti-armor (600 model) drones. Shaheds are much larger, cheap, low on capabilities, but attritable used to attack fixed positions (e.g., buildings). These are all very different.
I don't understand your point. Switchblades are (roughly) more akin to FPV (300 model) and Vampire drones (600 model) with reapect to size and payloads. Shahed style drones are roughly like like low end cruise missles. Different form factors and different capabilities. All of them are needed, but they're all very different.
A cruise missile is 3,000,000$ and a shahed drone is 50,000$ so if it’s even remotely the same capability it is an immense technological improvement over an expensive and slow to manufacture cruise missile.
You need a high/low capability that mixes all levels. For example, the Ukrainians and the Russians are both manufacturing very expensove cruise missles (Neptune/Iskander) and long range attack drones (shahed/fp-2/lute/etc). At any rate the original post I was responding to was comparing Switchblades to Shaheds, which is non-sensical.
If you do that you'll reset browser state with whatever you're replacing. For example things like scroll position, if the user opened an accordion, etc. would all be lost.
> Audio quality is decent here too. Listening to "Fast Car" now, and the quality is solid. :)
Fast Car was terrific, thanks for sharing! It is especially amazing considering this recording was made in 1988, just one month and one day (how poetic!) after Fast Car was released as a single.
reply