Yep, I get mobility work in pretty much every day. Generally at night after we've eaten dinner as a family, I'll do some mobility drills and foam rolling, etc., while we're doing other activities before bedtime.
Nobody is mentioning the elephant in the room: for sure many of the pagers where brought aboard commercial flights. So Israel seems to have an explosive that cannot be detected by the airport security, or they can confine usual explosives in a way that makes it undetectable by the standard means.
The docs at https://www.visidata.org/docs/ seem to contain any trivially remembered functionality for what I think of from a spreadsheet tool. I'm not a power user and couldn't describe how to use pivot tables, for example. Are there low-hanging features you miss from that page?
I agree that this is not going to satisfy something like 80-90% of people who just wanted Excel because a TUI is a nonstarter. I do think calling it "not even close" is unfair if we were strictly talking about functionality.
This looks more like a database interface and less like a tabular calculator.
Supposedly part of excels good design is it was always agnostic as to whether you're using it as a spreadsheet, poor man's database, or pretty table maker.
You seem shadowbanned and I had to vouch for this comment to make it visible. Your last comments seem ok, so maybe you want to mail dang (the moderator) about your account.
> Can’t we just store some data on disk and read / write from it when we need to? (Spoiler: no.)
I disagree. SQLite does a good job in uniting the 2 worlds: complex SQL queries with excellent data consistency and simple file(s). Although SQLite is for sure not the one size fits all solution.
> SQLite is for sure not the one size fits all solution
Nor is Postgres. PG is surprisingly versatile. E.g. with some extensions can be used as key-value storage (hashtable), document database, time-series db and so on. And it works quite well. Beyond "good enough" for many use cases. Added benefit, aside from having to run only one db-server, is that you can mix it: part relational, part document, etc.
But the PG versions nearly ever get as good as focused, dedicated solutions get. Which makes sense if you think about it: a team developing a dedicated key-value storage that does that and only that, for years, will always produce a better key-value storage then one bolted onto a generic RDBMS.
A practical example was where we used ltree extension to store ever growing hierarchies. We needed access control over subtrees (so that the X report for John only includes the entities of Johns devision and lower). While it worked in PG, it turned out that "simply replacing" it with OpenLDAP, which had all this built in, made it faster, easier and above all easier to maintain.
