Parity VS tokei

What got me interested in learning Rust with Ethereum is Reth (Rust Ethereum Execution Layer Client). OpenEthereum was another Rust client that got deprecated earlier in 2022, which is what I think inspired Reth to be made https://github.com/openethereum/openethereum . It sounds like Reth will go live in January/February 2023 https://github.com/paradigmxyz/reth#status they put out a summary here too https://www.paradigm.xyz/2022/12/reth

OpenEthereum | Programming Language = Rust

OpenEthereum v3.2.0 is ready for Berlin.

It's still maintained https://github.com/openethereum/openethereum

For Ethereum, there is Geth, OpenEthereum, Nethermind, among others.

I'm not sure why this was linked. Parity decided to stop developing their Ethereum client and this repo has been sitting unmaintained for about 2 years now, it will almost certainly not successfully sync with mainnet.

The Parity codebase was taken over by new maintainers and turned into OpenEthereum: https://github.com/openethereum/openethereum

However, writing and maintaining an Ethereum client is an exceptional amount of work with very little benefit, the primary OpenEthereum maintainers recently announced they would stop maintaining OpenEthereum and would start pouring their energies into an upcoming client called Erigon. https://medium.com/openethereum/gnosis-joins-erigon-formerly...

Erigon is a much better client.

Also, the Ethereum Foundation doesn't own a lot of the code used in the network. For example, lots of people use OpenEthereum as their client, which is not managed by EF.

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.