Translating the examples from the ReadMe, having read the file with:
$medias = Get-Content .\medias.csv | ConvertFrom-Csv
Previewing the file in the terminal xan view medias.csv
$medias | Format-Table
Reading a flattened representation of the first row xan flatten -c medias.csv
$medias | Format-List
Searching for rows xan search -s outreach internationale medias.csv | xan view
$medias | Where-Object { $_.outreach -eq "internationale" } | Format-Table
Selecting some columns xan select foundation_year,name medias.csv | xan view
$medias | Select-Object -Property foundation_year, name | Format-Table
Sorting the file xan sort -s foundation_year medias.csv | xan view -s name,foundation_year
$medias | Sort-Object -Property foundation_year | Select-Object -Property name, foundation_year | Format-Table
Deduplicating the file on some column # Some medias of our corpus have the same ids on mediacloud.org
xan dedup -s mediacloud_ids medias.csv | xan count && xan count medias.csv
$medias | Select-Object -ExpandProperty mediacloud_ids -Unique | Measure-Object; $medias | Measure-Object -Property mediacloud_ids
Computing frequency tables xan frequency -s edito medias.csv | xan view
$medias | Group-Object -Property edito | Sort-Object -Property Count -Descending
It's probably orders of magnitude slower, and of course, plotting graphs and so on gets tricky. But for the simple type of analysis I typically do, it's fast enough, I don't need to learn an extra tool, and the auto-completion of column/property names is very convenient.This is coming from a user with existing Kagi Ultimate subscription, so I'm generally very open to adopt another tool if it fits my needs).
Slightly offtopic, slight related: As already mentioned the last time Kagi hit the HN front page when I saw it: the best improvement I could envision for kagi is improved search performance (page speed). I still encounter multiple second page loads far too frequently that I didn't notice with other search engines.
How does the wet preservation work?
Random passwords, write-only attributes (like database master passwords) are the most common.
How do you express “create a DB with this strong password, then put it in a s3 object”, then later “actually put it in SSM rather than s3”?
With Bicep, we mostly deploy only the initial state and then we either re-deploy the whole thing or, if this isn't possible due to the interruptions this causes, add migration scripts in an imperative language (az cli/ pwsh). Which is admittedly the much less elegant approach.
How can you express this without state? Or more generally, any “random_password”, “random_choice” etc, or even anything that is a “write only” property
You can’t. So this is dead in the water.
Do you in practice really use random names? In my experience, I'd just use a loop vm01...vm10 for the names and the passwords aren't needed to identify an instance after the deployment so here randomness isn't an issue.
I've used qr codes maybe... 6 times, ever?
With probably 50% success rate before I give up.
I know for a fact that literally nobody else in my in law family of middle class Canadians has ever used a single one.
Anecdata of course, but if we're sharing assumptions... :-)