node-seccomp VS tldr

I was exploring the actual implementation[0] of a capabilities feature in Nodejs and was utilising seccomp (via libseccomp) on Linux at least to achieve a greater degree of security than might otherwise be possible by remaining in userland code. The idea is that you'd write your code, import whatever you like and define your capabilities upfront at initialisation. The problem is there's quite a big disconnect between what you are doing in JavaScript and what's happening with system calls in v8, libuv and the other native parts that it's difficult to predict what you need to block and what's actually going to happen. So I don't think my approach is really viable in a general sense, although capabilities in general I think would improve the situation if the wider community were to adopt the approach.

[0]. https://github.com/roryrjb/node-seccomp

Maybe this already helps: https://github.com/tldr-pages/tldr

A bit of an aside, but I really like "guides to things we otherwise take for granted". So few man pages are built around example use cases, but those are often what make the case for a tool!

A similar spirit to projects like https://github.com/tldr-pages/tldr/ , but this has a lot more useful detail.

The ripgrep author has a blog post on performance and benchmarking that is an interesting read in itself: https://blog.burntsushi.net/ripgrep/

Looks like bro pages is archived and they recommend https://github.com/tldr-pages/tldr or https://github.com/cheat/cheat

a very excellent tool to grab is TLDR https://tldr.sh/

And that's why tldr is such a powerful tool! You can easily install it with sudo apt install tldr or follow this demo.