The difference here is that katacontainers are OCI and CRI complaint - meaning that it can immediately be used with K8s, Nomad and possibly others. You get all the features of these orchestration platforms. LXC doesn't have that (it actually predates OCI and CRI).
There are other orchestration systems that can use LXC - LXD, libvirt, Proxmox, and may be others. Also, LXC doesn't have traditional virtualization - that's a feature of LXD using KVM. (Do you mean system containers, as opposed to regular app containers?)
Great product from a great team!
Pretty expensive for non-casual searching, I do a lots of searches in a day. Currently self-hosted SearchXNG does the trick but would love to start use Kagi for all.
Would love if they manage to find ways to increase limits or reduce pricing.
We can use uBlock for ads + ddg for results, but for masses and in general for healthier search engines I would be happy to use Kagi daily.
It depends a lot on the project and your CPU. Incremental build (build, change 1 thing, rebuild) times are affected more than clean build times, because linking is a larger % of an incremental build.
When I benchmarked it about a year ago (with a fairly large Rust project on a 24-core machine), incremental builds went from ~8s to ~2.7s.