body { -ms-overflow-style: scrollbar; overflow-y: scroll; overscroll-behavior-y: none; } .errorContainer { background-color: #FFF; color: #0F1419; max-width: 600px; margin: 0 auto; padding: 10%; font-family: Helvetica, sans-serif; font-size: 16px; } .errorButton { margin: 3em 0; } .errorButton a { background: #1DA1F2; border-radius: 2.5em; color: white; padding: 1em 2em; text-decoration: none; } .errorButton a:hover, .errorButton a:focus { background: rgb(26, 145, 218); } .errorFooter { color: #657786; font-size: 80%; line-height: 1.5; padding: 1em 0; } .errorFooter a, .errorFooter a:visited { color: #657786; text-decoration: none; padding-right: 1em; } .errorFooter a:hover, .errorFooter a:active { text-decoration: underline; } #placeholder, #react-root { display: none !important; } body { background-color: #FFF !important; }

JavaScript is not available.

We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using twitter.com. You can see a list of supported browsers in our Help Center.

Terms of Service Privacy Policy Cookie Policy Imprint Ads info © 2023 Twitter, Inc.

Conversation

Replying to

and

I mean really if shared memory space is the particular concern y'all need to stop writing C++ and write some fricken Rust :)

1

1

You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more

You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more

Replying to

and

Hey, not saying you disagree, just saying I think that's part of the pitch for

's work - enable experimentation by making it easier to build other clients written in other languages in the same process by linking the original consensus code (and no more) in.

1

2

Replying to

and

So, so, so much less thought has to be given to the API layer being "unsafe" if you write it in a memory-safe language (esp if you put sane limits on eg memory usage and run it in its own threads).

1

1

You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more

You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more

You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more

Replying to

and

I dunno. I have several cleaner rewrites of the p2p layer I’d love to run instead :). Maybe I’ll be the only one, though.

1

3

You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more

Replying to

and

Add Parallel P2P Client in Rust by TheBlueMatt · Pull Request #17376 · bitcoin/bitcoin

This was actually the original goal of the Rust work, but we had to start somewhere a bit simpler. This adds a full parallel P2P client, written in Rust, which can download and serve both headers a...

3:38 AM · Dec 21, 2021

Show additional replies, including those that may contain offensive content

Show