bonsaidb VS tokei

I do have ideas in the issue tracker on some of the next steps towards an actual migration system.

What about https://github.com/khonsulabs/bonsaidb? Progress seems stall since last summer but very cool project

There is Nebari which is the KV part of BonsaiDB I've used both successfully (and that is currently in production)

In BonsaiDb, I define entire test suites as macros. This crate has a common trait that has multiple implementations in different crates. Each implementation needs to be tested thoroughly. For cargo test to be able to work in each crate independently, I needed to have the #[test]-annotated functions in the crate being built. By using a macro, I can define the functions in one location and invoke the macro in each crate to import the test suite into that crate.

hey, just letting you know that there already is a project called bonsai-db and some people might confuse bonsai-bt as part of that project

I'm finishing up a large refactor of BonsaiDb which will add support for using BonsaiDb in non-async code.

I'm working on a major refactoring of BonsaiDb, aiming to improve the design of several interrelated features. While it started by aiming to enable a non-async interface for BonsaiDb, I realized mid-refactor that another major refactor would be better to do simultaneously rather than separately. Thank goodness that refactoring in Rust is such a wonderful experience!

It depends on what you mean by "support graphs". If you mean support the abillity to build a GraphQL interface in front of it, yes that is already possible in a limited fashion, although there are no first-class relationship types yet.

I'm trying to release the first alpha of BonsaiDb. I'm wrapping up replacing OPAQUE with Argon2, in an effort to make upgrading less likely to cause issues in the future (given that OPAQUE is still a draft protocol). I still love OPAQUE and will bring it back in the future.

So If we would only count code and not comments, it is only 9489 LoC Rust. Which would be about 0.03% and if we take all lines and not only LoC it would be around 0.05%

[0] https://github.com/XAMPPRocky/tokei

[1] https://github.com/torvalds/linux/commit/b401b621758e46812da...

thirdly: found this (https://github.com/XAMPPRocky/tokei) and wanted to analyze languages used on my system, didn't see a package manager (apt) for it that I had. So i installed cargo via apt-get rustup. Added the bin folder to $PATH via PATH=$PATH:~/.cargo/bin. But did not make it permanent. And stupidly rand tokei on "/", realizing how long and unhelpful that would be killed it. Then ran it in a dump folder with some very nested repo dumps, and tons of wolfram.nb files. After killing that too, and attempting to kill via system monitor. Still have two of those as zombie processes.

tokei

For what it's worth, tokei seems to be named after tokei.

BTW, for more info on how it is done, you can check out tokei which is the library use by onefetch for code statistics.

With pytokei you can count code quickly using all the power from tokei, but from python.

Tokei is a nice utility to count lines and stats of code. It is very fast, accurate, and has a nice output. It supports over 150 languages and can output in JSON, YAML, CBOR, and human-readable tables.