They are different, and the biggest reason is (I suspect) that a Zulip workspace is self-contained while a Matrix server is able to federate with other Matrix servers.
Other European institutions are also adopting Matrix, so federation may turn out to be an important feature.
Just because the hooks have the label "pre-commit" doesn't mean you have to run them before committing :).
I, too, want checks per change in jj -- but (in part because I need to work with people who are still using git) I need to still be able to use the same checks even if I'm not running them at the same point in the commit cycle.
So I have an alias, `jj pre-commit`, that I run when I want to validate my commits. And another, `jj pre-commit-branch`, that runs on a well-defined set of commits relative to @. They do use `pre-commit` internally, so I'm staying compatible with git users' use of the `pre-commit` tool.
What I can't yet do is run the checks in the background or store the check status in jj's data store. I do store the tree-ish of passing checks though, so it's really quick to re-run.
There are two layers, both relating to concentration.
Driving a car takes effort. ADAS features (or even just plain regular "driving systems") can reduce the cognitive load, which makes for safer driving. As much as I enjoy driving with a manual transmission, an automatic is less tiring for long journeys. Not having to occupy my mind with gear changes frees me up to pay more attention to my surroundings. Adaptive cruise control further reduces cognitive load.
The danger comes when assistance starts to replace attention. Tesla's "full self-driving" falls into this category, where the car doesn't need continuous inputs but the driver is still de jure in charge of the vehicle. Humans just aren't capable of concentrating on monitoring for an extended period.
IMNSHO yes. But not necessarily so drastically -- a VW (to pick an example I've seen evidence of: https://www.thedrive.com/article/10131/the-volkswagen-arteon...) will ping at you if you stop touching the steering wheel for ten seconds or so, and will actively monitor to make sure your attention is on the road. A Tesla won't, or at least wouldn't in 2018, to the point where someone was convicted of dangerous driving having climbed into the passenger seat while driving along the M1: https://www.bbc.co.uk/news/uk-england-beds-bucks-herts-43934...
You should probably be running your renewal pipeline more frequently than that: if you had let your ACME client set itself up on a single server, it would probably run every 12h for a 90-day certificate. The ACME client won't actually give you a new certificate until the old one is old enough to be worth renewing, and you have many more opportunities to notice that the pipeline isn't doing what you expect than if you only run when you expect to receive a new certificate.
There's a linear buffer of pages, most of which come from the pool. It's not clear to me under what conditions these are returned to the pool? Is it when the specific session terminates?
When a non-standard page reaches the point of being recycled, it'll instead be re-added to the list but with a standard size. That effectively leaks the extra space above the standard size. But when the buffer is released (because the session ends?) the pool is also released, which releases all the standard sized pages but leaks the custom-sized ones?
Which suggests that the issue may be even rarer than it initially looked to me: I tend to open a small number of sessions and then use them continuously, rather than starting new sessions during the lifetime of the process. If I never terminated a session, I would never fully leak the memory?
In part a follow-on from the Stack Overflow thread, when I was younger I found various "how to ask questions" articles to be really useful (I particularly recommend Jon Skeet's https://codeblog.jonskeet.uk/2010/08/29/writing-the-perfect-...). But he's focused on asking questions of "the Internet", where there should be no expectation that a random netizen will put effort into answering.
That's not necessarily the case at work with colleagues, so I wrote this article to fill a perceived gap.
Other European institutions are also adopting Matrix, so federation may turn out to be an important feature.
reply