Implementing truly safe semaphores in rust, and the costs we pay for safety

China’s Phytium D2000: Building on A72?

Distributed System Models in the Real World

Issue #275

10/5/2022

{{PreviewText}} 

Hello
Sorry that there were no issues on Monday and Tuesday; I've been traveling.
A reader shared this pretty cool library for keeping your bash history in sync across different servers.
Here's a bunch of resources on using WSL (Windows Subsystem for Linux).
Anyway, here's the issue.

====================================================================

Today's Sponsor: Could be you!

Are you or your company interested in sponsoring the newsletter? Feel free to reach out to me by replying to this email or clicking the link above.

====================================================================

Implementing truly safe semaphores in rust, and the costs we pay for safety

Published: 2 October 2022
Tags: rust

Mahmoud Al-Qudsi discusses the concept of "zero-cost abstractions" in programming, which is the idea that abstractions should not incur any additional runtime cost. The Rust programming language is used as an example of a language that embraces this concept. Mahmoud goes on to implement a semaphore type in Rust.


====================================================================

China’s Phytium D2000: Building on A72?

Published: 28 August 2022
Tags: benchmarking, cpu

In the past few years, China has been investing heavily in homegrown microprocessors. Phytium's D2000 is one example of a homegrown design. The chip targets desktops, laptop, and industrial applications. It consists of eight FTC663 ARM cores running at 2.3 GHz, arranged in clusters with two cores each. The author, clamchowder, takes a close look at the D2000, running a few workloads and providing context on where D2000 stands.


====================================================================

Distributed System Models in the Real World

Published: 19 September 2022
Tags: architecture, distributed systems

Kevin Sookocheff discusses the different components of a system model for a distributed algorithm. These components are processes, communication links, and timing assumptions. Kevin explains how these components can be varied to represent different operating environments, then highlights the benefits of working with a system model.


How did I do?

5 4 3 2 1
Amazing


Bad

Want to help?
Thank you for reading! If you enjoy the newsletter, I would really appreciate you helping me spread the word by forwarding this to your friends and colleagues or sharing it on social media! Get cool stuff for your referrals using your link https://abyteofcoding.com.

Your referrals:


If you want to discuss or comment on this issue, head on over to this page at A Byte of Coding. You can also subscribe there if you're new!

Have comments or feedback? Just reply to this email or hit me up on Twitter @AByteOfCoding.

Email landed in your promotions tab? Please move it over to primary so you don't miss the latest issues in the future.
Thanks for your Support! 
Big thanks to all of the Patreon supports and company sponsors. If you want to support the newsletter you can checkout the Patreon page. It's not necessary, but it lets me know that I'm doing a good job and that you're finding value in the content.


Stats (updated daily)

Sent: 2988

Opens: 1446

Clicks: 515

Link Clicks Clicks % Unique Clicks Unique Clicks %
Implementing truly safe semaphores in rust, and the costs we pay for safety 112 34.89% 118 34.91
China’s Phytium D2000: Building on A72? 49 15.26% 53 15.68
Distributed System Models in the Real World 160 49.84% 167 49.41

Previous

Back to Issues

Next