Eric Biggers (Google) on why the Linux kernel's crypto API is hard to use and slow — dynamic allocations, indirect calls, abstraction that fits neither modern algorithms nor modern hardware.
It's a bit hard to comprehend that's reality to be honest.
But I could see that it could be the case from the fact that old industrial factories or old corporates would still run with what works for them.
Systemd v261 has been released, some changes are including:
- a new IMDS (Cloud "Instance Metadata Service") Subsystem
- "boot secret" functionality for use on systems that lack a physical TPM
- support for the kernel's Live Update Orchestration (LUO) / Kexec Handover (KHO) systems when they are present and enabled
Understood. Didn't mean as a click-bait or something. Just sharing my cli report summarize.
Target user here in HN should be tech-savy and this tool is not designed for non-tech because it is required highly customized from user to get the result user want.
Anway, would you mind putting the correct title here ? I will consider to update.
Understood. Let me give some examples, most of the time we don't need spaces between table output, git diff produce bunch of unnessary info we just need filename and actual diff lines, kubectl describe we would mostly check for events, image etc etc.
This is the reason why I make it as composable filters as it very depends on your specific ops to optimize the token.
To be safe if you need a full json, would make conditonal passthrough as the original raw output. Or, need to handle selective object using python via the filter plugin.
Thanks for your feedback. Will put this in place. Meanwhile, please checkout architecture doc and plugin. The plugin doc could a little bit giving insight of what it does.
In term of token saving performance, it should be on par with rtk since it is basically the same idea.
The major different is rtk bundled hundreds of filter logic and no room for user to adjust without maintaing user owned fork or opening the pull request while lowfat is using opposite architectural approach by removing almost all filter logic in the binary and seperate user filters as a plugin system