Parity VS rust

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.

Here's an example of someone citing a disagreement between CRT and shell32:

https://github.com/rust-lang/rust/issues/44650

This in addition to the Rust CVE mentioned elsewhere in the thread which was rooted in this issue:

https://blog.rust-lang.org/2024/04/09/cve-2024-24576.html

Here are some quick programs to test contrasting approaches. I don't have examples of inputs where they parse differently on hand right now, but I know they exist. This was also a problem that was frequently discussed internally when I worked at MSFT.

    #include 

> instead of choosing a certain numbered version of the random library (if I remember correctly) I let cargo download the latest version which had a completely different API.

Yeah, they didn't follow the instructions and got burned. I still think that multiple things went wrong simultaneously for that experience. I wonder if more prevalent uses of `#[doc(alias = "name")]` being leveraged by https://github.com/rust-lang/rust/pull/120730 (which now that I check only accounts for methods and not functions, I should get on that!) so that when changing APIs around people at least get a slightly better experience.

Almost fixed the compiler: https://github.com/rust-lang/rust/pull/123325

Rust: A secure, efficient, and modern programming language (omitting ten thousand words). You can simply follow the installation instructions provided on the official website.

Recently did something similar in Rust but for generating SVGs. We've adopted it for snapshot testing of cargo and rustc's output. Don't have a good PR handy for showing Github's rendering of changes in the SVG (text, side-by-side, swiping) but https://github.com/rust-lang/rust/pull/121877/files has newly added SVGs.

To see what is supported, see the screenshot in the docs: https://docs.rs/anstyle-svg/latest/anstyle_svg/

We strongly believe in Rust as a powerful language for building production-grade software, especially for systems like ours that run alongside Kubernetes.

The above Assert<{N % 2 == 1}> requires #![feature(generic_const_exprs)] and the nightly toolchain. See https://github.com/rust-lang/rust/issues/76560 for more info.