I switched to zim years ago and found it has all the features that I need but is much faster and I think easier to install (though I haven’t installed either for some time).
Fast as sin, and one of the most flexible installers systems. You can point it at an incredibly diverse array of different things to install, in different forms, with different urls, and it will just do the thing.
Zimfw definitely has it's own ecosystem, plugins which are zimfw capable. But it's remarkably versatile at bringing in zsh code. Most plugin-systems are pretty ego-centric, demand specific implementations, and zimfw stands out not just for it's ridiculously impressive speed & handling, but for it's versatility too.
Whenever there are stories about bushfires in Australia there is inevitably discussion about how the regeneration is amazing and how fires are part of the ecosystem. While this is true to an extent, it is important to point out that in recent years due to climate change the frequency and intensity of the fires is causing huge ecosystem change to areas that are burnt multiple times before they can recover.
This is really cool, one thing that would make it much more useful for me is to have the ability to easily select which project you want to use, especially if it could have the same fuzzy search as resources. My company has hundreds of GCP projects. At the moment it seems like I'd have to set up individual configurations for each project.
Both of them are already supported. To select the project you can type @ and it will show you the list of available project. The fuzzy search is also already supported.
Yeah my bad. @ will show configurations. So you can set up your configurations to point a specific project(gcloud config set project PROJECT_ID) and then when you use @ and select a specific config and access the resources the project is auto applied to the urls and for resource searches as well
I found that liquibase doesn't really support rollbacks, particularly with mysql as you can't do transactions for schema updates, if the migration fails in the middle of an update it just gets left in a half-updated state.
Liquibase does support rollback DDL with MySQL; I used it.
I put each DDL in a Liquibase changeset with a corresponding rollback DDL I constructed by hand. If the Liquibase changeset failed, I could run the rollback for all the steps after the "top" of my wish-I-could-put-them-in-a-MySQL-transaction operations.
But you are right MySQL itself doesn't support transactions for DDL and that is true whatever tool you use.
It is true that if you put multiple SQL operations in a single Liquibase changeset that are not transactional you can't reliably do rollbacks like the above.
It is also true that constructing an inverse rollback SQL for each changeset SQL by hand takes time and effort particularly to ensure sufficient testing, and the business/technical value of actually doing that coding+testing may or may not be worth it depending on your situation/use-case.
I tried using wanderlog on a recent 4 month long trip and it became totally unusable after adding maybe 2 months worth of things to it. It has some really baffling UI/UX decisions too, like not showing the address of accommodations, just the name. Really made me feel like no one working on it had ever tried to use it when actually traveling.
They had also gone big on AI slop for recommendations which made it really hard to trust any advice in the lists of things to do.
I think these sort of travel apps are really hard to find an audience for. Very very few people travel often enough to pay a subscription and it is hard to justify spending significant money as a one-off purchase when traveling is already so expensive.
I'm surprised that more comments aren't mentioning this. I've recently moved from a stack managed by AWS CDK to one managed by Pulumi on GCP and the difference is stark. The building blocks that AWS provides allow spinning up complex services with relatively minimal configuration. The pulumi code required to create a simple GCP cloud run service with IAP behind a load balancer is literally hundreds of lines.
Plus GCPs documentation is far far worse than AWS's.
This is great, I don't have a concrete use-case right now but can definitely see myself returning to this in the future. One thing that would be handy is having a way to either accept a ffmpeg cli command, or convert from a cli command to the typescript syntax. My experience with ffmpeg if you often do a lot of copying and pasting of commands from documentation or random guides, it'd save a bit of time if you didn't need to transcribe the commands into streampot's syntax.
Chat GPT has been a game changer for my ffmpeg usage. Instead of cobbling together commands from StackOverflow questions and guides, I just describe what I want in plain English and it's got a pretty damn good success rate for giving me what I need.
FWIW I found the whole video quite interesting, I had never really considered that there could be sound recordings from before anyone had thought of a way to play them back.
Though I do remember an old mythbusters episode [1] where they tested whether it was possible for audio to be "accidentally" recorded on a pot when a piece of grass happened to mark the pot while spinning.
I don't think this was a real myth. This was an X-Files episode in which a clay pot that has been molded while Jesus was ordering Lazarus to rise from the dead could be used to bring other people back from the dead by playing back the recording. If I'm remembering correctly, even in X-Files this was actually a hoax.
That X-Files episode may have been inspired by "Time Shards" [1] by Gregory Benford, a short story first published in 1979.
TLDR: Too late to be included in the bi-millenium vault, a Smithsonian researcher discovers an audio recording accidentally inscribed on a c. 1280 pot by a pointy tool cutting a decorative spiral. After listening to the banal conversation recorded on the pot, the researcher wonders about the contents of the vault to be opened in a thousand years: “What makes you think we’ve done any better?”
As so often, Daedalus (David E H Jones) got there first with one of his semi-humorous articles in New Scientist in 1969 - one of those collected in "The Inventions of Daedalus" in 1982.
https://zimfw.sh/
reply