#erlang

See tagged statuses in the local BookWyrm community

A critical vulnerability, named BatBadBut, was discovered in the Rust programming language, affecting not just Rust but also Erlang, Go, Python, Ruby, and potentially others. This vulnerability, with a severity score of 10/10, could allow attackers to execute arbitrary commands on Windows systems by exploiting how Rust handles batch files. The issue arises from Rust's standard library improperly escaping arguments when invoking batch files on Windows, leading to potential command injection. The vulnerability has been addressed with a fix in Rust version 1.77.2, which developers are urged to update to. Other programming languages and systems, including Node.js, PHP, and Java, are also affected and are working on patches.

https://flatt.tech/research/posts/batbadbut-you-cant-securely-execute-commands-on-windows/

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

I’m proud to introduce Urlang (𒋀𒀊𒅴)! Finally you can program in cuneiform!

Smart Contracts? Don’t use Ethereum. Cuneiform contracts will be around long after your blockchain has died!

Looking to create an AI bot to write Amazon reviews? Cuneiform has been roasting products since the dawn of written language.

Or maybe you just want to write apps for a Babylonokia.

Don’t forget to drink lots of EuphratesWater™ to achieve peak performance while programming in Urlang!

Complaint tablet to Ea-nāṣir thought to be the oldest written complaint written in Cuneiform on a clay tablet. It complains that the copper was sub-standard and that his servant who was handling the transaction was treated rudely By Geni - Photo by user:geni, CC BY-SA 4.0, https://commons.wikimedia.org/w/index.php?curid=142014918
Contract for the sale of a field and a house in the wedge-shaped cuneiform adapted for clay tablets, Shuruppak, circa 2600 BC. By Unknown artist - Marie-Lan Nguyen (2005), Public Domain, https://commons.wikimedia.org/w/index.php?curid=407203
A BabyloNokia: a clay tablet shaped like a mobile phone with Cuneiform writing on the display and buttons By Karl Weingärtner (User:Kalligrafiemonk) - Own work, CC BY-SA 4.0, https://commons.wikimedia.org/w/index.php?curid=56370415

Does anyone know a more accessible explainer about libcluster topologies?

My use case is that most nodes need to connect to every other node, but there are one or more “special” nodes that should only connect with each other and I can’t figure out which strategy to use to prevent them from auto connecting 🤔💭

I don't yet know how to efficiently answer questions about the Swift language, so forgive if the answer is obvious.

Erlang/Elixir have a fault-intolerance library built on top of their version of actors. https://en.wikipedia.org/wiki/Open_Telecom_Platform It involves "supervision trees”, where supervisors control the lifespans of actors they supervise, react to unexpected failures, etc.

Is there an equivalent library for Swift?

It is incredibly tempting to interpret and implement ActivityPubs concept of an Actor as an Elixir GenServer/actor. Mailboxes and message passing.

If I was building it out as an in-memory system this could be fun but for typical needs it is conflating runtime characteristics with the outward protocol.

Lining those up would make the system simple to reason about in particular ways. I might do the experiment.