I now have #Erlang in #OpenBSD and #Fedora #Silverblue. Just for fun. Not anticipating profit.

Here's the customary #introduction: i'm into #C and tolerate C++ on a daily basis at work, i've also used others like java, kotlin, python, PHP, etc and am curious about #COBOL, #AdaLanguage and #erlang.

My dislike of jenkins is only surpassed by my hate of githubactions and everything MS-related. AI is not I, only A. I'm interested in #selfhosted stuff but atm that's a VPS with some sites, which doesn't really count. For now #syncthing is quite useful and #wireguard is on the horizon once i reformat/reinstall my current #gentoo (i'll keep the root #ZFS aproach and am on the fence regarding #XFCE or #KDE), would be interesting to have a barebones #KVM/#QEMU running all the stuff and i digress.

kthxbai\0

I was wondering how to give compile time configuration to Elixir dependencies in a Gleam project and came up with this kludge: https://blog.nytsoi.net/2025/06/28/gleam-elixir-compile-config

New GreyNoise Labs research: CVE-2025-4748

Our team demonstrates how path traversal via zip archives can be used to achieve file write and code execution against Erlang OTP environments, exploiting CVE-2025-4748. This technique leverages the zip:unzip function when untrusted zip files are extracted.

Read the full technical breakdown here: https://www.labs.greynoise.io/grimoire/2025-06-17-erlang-zip/

The AtomVM has a new website: https://atomvm.org/
#Erlang #Beam

Does any one have link to the source of the original Joe Armstrong’s JAM (Joe’s Abstract Machine) for the original #Erlang before BEAM came about? JAM was a stack machine, BEAM is a register Machine. Just trying to understand how it operated, I understand it did some interesting things with the stack. #stackmachines #abstractmachine #virtualmachine #programminglanguages

New in distribution at Pragprog -
The book guides you through the Erlang standard library and how you can leverage it from Elixir as well as structuring applications to make the most out of BEAM.
https://pragprog.com/titles/d-akelixir?utm_source=m
@akoutmos
#ElixirLang #Beam #Erlang

That’s not so super exciting once you know the true cause of all of this.

The believe and full trust in the ten times programmer who then fucks up and wrecks it all with just a single debug line of code that went unnoticed.

But sure let’s write a whole book about it because we‘re old white guys and can’t admit to failure.

https://mastodon.social/@lobsters/114627006557032798

I haven’t read it, so now come and grill me!

Took some time out of vacation today to publish Rebar3 3.25.0 for #Erlang 28.0 compatibility: https://github.com/erlang/rebar3/releases/tag/3.25.0

Hey @dch thank you for prividing https://people.freebsd.org/~dch/pub/tailwind/ !

I wasn't able to find the build script nor a FreeBSD port. Before I venture into this any further - would you be so kind and share the build script?

Erlang is like “what if go but prolog”

(Yes I know Erlang came first and Go descended from a long line of similar languages and CSPs are the bomb and a common source of inspiration just go with it.)

Is Node.js the future of backend development, or just a beautifully wrapped grenade?

Lately, I see more and more backend systems, yes, even monoliths, built entirely in Node.js, sometimes with server-side rendering layered on top. These are not toy projects. These are services touching sensitive PII data, sometimes in regulated industries.

When I first used Node.js years ago, I remember:
• Security concepts were… let’s say aspirational.
• Licensing hell due to questionable npm dependencies.
• Tests were flaky, with mocking turning into dark rituals.
• Behavior of libraries changed weekly like socks, but more dangerous.
• Internet required to run a “local” build. How comforting.

Even with TypeScript, it all melts back into JavaScript at runtime, a language so flexible it can hang itself.

Sure, SSR and monoliths can simplify architecture. But they also widen the attack surface, especially when:
• The backend is non-compiled.
• Every endpoint is a potential open door.
• The system needs Node + a fleet of dependencies + a container + prayer just to run.

Compare that to a compiled, stateless binary that:
• Runs in a scratch container.
• Requires zero runtime dependencies.
• Has encryption at rest, in transit, and ideally per-user.
• Can be observed, scaled, audited, stateless and destroyed with precision.

I’ve shipped frontends that are static, CDN-delivered, secure by design, and light enough to fit on a floppy disk. By running them with Node, I’m loading gigabytes of unknown tooling to render “Hello, user”.

So I wonder:
Is this the future? Or am I just… old?

Are we replacing mature, scalable architectures with serverless spaghetti and 12-factor mayhem because “it works on Vercel”?

Tell me how you build secure, observable, compliant systems in Node.js.
Genuinely curious.
Mildly terrified and maybe old.

With a little bit of tweaking and a lot of waiting, I got the Tigerbrew formula for #Erlang to succeessfully build under Mac OS X Leopard on my eMac. eMac = "erlang Macintosh", amirite?

The #s390x open source software team at IBM confirms the latest versions of various software packages run well on #Linux on #IBMZ & #LinuxONE

In March 2025 validation was maintained for over 30 projects, including #Ansible, #Apache Tomcat, & #Erlang

Plus, community CI was added for segyio, and Rust's linux_syscall project now publishes s390x releases on crates.io

Full report + how your project can apply for a s390x VM: https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/elizabeth-k-joseph1/2025/04/18/linuxone-open-source-report-march-2025

we talk about ssh with @jtk and bam there is this

https://vulnerability.circl.lu/vuln/CVE-2025-32433#sightings

“SSH server (Erlang) may allow an attacker to perform unauthenticated remote code execution (RCE).”

We should be careful when we talk.

Having packages/modules be defined as single files is a fundamental programming language design error. #Python, but also #Erlang, #Scheme, the misguided package-inferred-system extension for #CommonLisp… Because no one wants a 10k lines file mixing dozens of concepts, you end up with a multitude of small packages for no good reason.

At least in Erlang you can just use whatever was loaded without manually importing every single module you need everywhere, but Python is as usual the worst.

At long last, my use of emojis is no longer restricted

https://bsky.app/profile/jola.dev/post/3lmwn24gqgs2x

I have been messing around with Erlang -- kicking the tires, as it were

https://learnyousomeerlang.com/content

https://www.erlang.org/doc/readme.html