Who do you know who wants to come work full time on #ElixirLang OSS tooling? (Boosts appreciated!) jump.ai/careers?ashb... #ElixirJobs

The power of pattern matching for implementing protocols! Nelson Vides at @codebeam.bsky.social

Daniil Popov & David Bourgeois: Elixir powers Super Bowl & Olympics broadcasts. Billions watch on BEAM.

Really interesting pros and cons in choosing ports over NIFs on today's @codebeam.bsky.social keynote!

Naturally the day it's @codebeam.bsky.social close to my actual home the trains don't go and going there becomes a nightmare

Released: Benchee 1.5.0! Highlights: * The elixir 1.19 compilation warnings are gone! * There is now a `max_sample_size` to deal with issues of too large samples * outlier removal is finally in github.com/bencheeorg/b...

the rubygems and bundler projects continue to change hands with nobody having ever explained how they came to be in the possession of ruby central www.ruby-lang.org/en/news/2025...

Elixir 1.19 released! 🎉 This one had a lengthier rc period. It brings type system improvements and compile time improvements in large projects among other things 🚀 elixir-lang.org/blog/2025/10...

Ruby Central said some really concerning things today. I don’t think they’re representing the situation accurately. andre.arko.net/2025/10/09/t...

This. And all framed as “not taking sides” or “jumping to conclusions.” Most of the upset with RC was about lack of comms, kicking out people on GitHub, and platforming DHH, none of which have been sufficiently addressed.

Ruby community: Look, we can be angry about what's happening, we can raise our complaints, but under no circumstances should anyone _ever_ harass someone's families, coworkers, or friends. That is completely unacceptable, and wholly against the ethos of the language. We must do better.

the reason I advocate for projects to have a code of conduct is because harassment is never okay. not only is harassment never okay, harassing families and coworkers is even worse. get out of here with that.

Another 🔥 package release from @maennchen.dev 😎 AshDiagram is a library for generating beautiful diagrams to visualize your #AshFramework applications. Generate Entity Relationship, Class, C4 Architecture, and Policy diagrams directly from your Ash resources and domains. 🚀

It's incredible how this whole thing has cut to literally every important cultural and political question in OSS. These are the big questions, the values you build communities around. We should be clear about the things we believe. We coasted on the status quo and differences are now clear.

Me: DHH is saying some kinda racist stuff, and he’s outright bullying people in PRs. Them: But look over here! André had a gap in his commit history! And he once got paid $150 / hour to do *open source*!!! Outrageous! 😲😲😲

The way that certain people in this community attack André, while turning a blind eye to DHH’s (objectively far worse) behaviour. It’s fucking disgraceful.

Didn't read bluesky for a weekend. Immediately completely out of date on what's currently going on. Hot damn people. What a mess. About a year ago I had "Community" down as probably the biggest factor in favor of Ruby - and a huge at that. This all _significantly_ weakens that point.

The AlchemyConf version of my "Tell me a Story" talk is finally out 🎉 content.subvisual.com/talk-roundta...

I went through Ruby Together's old Form 990s with the IRS: 1. Andre never reported more than $60k in compensation to himself in a year. Seems pretty reasonable to me. 2. Meals/travel/IT expenses are about $20k year, roughly ~6.6% of revenue, which to me is reasonable.

"[you] discovered that people with no active affiliation or agreement in place had top level privileges to some of this critical infrastructure." The people you removed about were actively paid for contractual on-call support through Ruby Central. Far from unaffiliated.

I really appreciate your post @apiguy.dev. Thank you for posting your thoughts. I wish you had the info I had to make your decision. Here's the core issue: Before Sept 9, when a trusted maintainer broke our shared contract and added an RC non-maintainer, you had no ability to enact your vote.

The Ruby community deserves to know who voted for this and what information they were acting on. Ruby Central is actually very opaque. They don’t publish donations, they don’t publish votes, the community has no say who’s on the board. There is no accountability.

Today has been... intense. Thank you everyone who's discussed this with me and offered kind words or support. I don't know the intent behind what happened. The people involved aren't villains, and they aren't evil.

- This is a bad day and a bad look for the entire Ruby ecosystem. It makes those of us who actively promote Ruby use for projects look bad. RubyCentral citing "supply chain issues", presumably referencing NPM, in the Ruby ecosystem which handles these dramatically better is unnecessary FUD.

- Timeline: RubyCentral had the offer of mediation (from me, others) yesterday, met with me, knew I was meeting with RubyGems maintainers today, engaged with the governance proposals in github.com/rubygems/rfc... yesterday, pulled access to maintainers shortly after, announced what they did today.

Having met with both sides on the current RubyCentral/RubyGems situation, here's my take: - RubyCentral have managed this exceptionally poorly in many ways including removing literally the most active member of the RubyGems organisation by mistake who has declined to return

So who's taking bets on how @rubycentral.org / #rubygems unfolds after their first response? Double down or "we're sorry to have violated your trust"? (I acknowledge there is a possibility of important context missing, but since it was not included in the first reply... unlikely)

like, this does not answer any of the questions this event has raised about why the existing team was considered not qualified to continue their work, or even have the end of their repo access clearly explained to them. how does booting the existing team contribute to any security goals

Ruby Central reply dropped. A focus on security is good, taking away access from maintainers diligently doing their work for many years is not. It sounds a bit like suspecting everyone by default, which I hope is not their intention. Also why this quickly without a conversation beforehand?

oof, what a disappointing way to end more than 15 years of open source work. (summary by @duckinator.bsky.social at pup-e.com/goodbye-ruby...). good luck to the remaining RubyGems team, and it’s time to focus my energy on new projects that I’m truly excited about, like rv.dev

Hey, #ruby folks! I've been one of the #RubyGems maintainers for the last decade. Ruby Central has forcefully taken control of the RubyGems organization on GitHub, the `rubygems-update` and `bundler` gems on rubygems[.]org, and more. You can read the details here: pup-e.com/goodbye-ruby...

Some pictures of the afternoon lineup. We learned about the importance of teamwork, the wonders of the Ash framework, why “lagom” is the best way to go and even how to write a book! #goatmire #elixir

What a great start at the last day of #goatmire in Varberg. Both live music and an amazing puppet show, all analogue! #elixir

With Goatmire in the bag. I am resting for a minute but shortly the call of the community horn sounds again and we plan to answer. As part of Global Elixir Meetups we are making an Elixir meetup in Göteborg. luma.com/g7hqffz7 Open to speaker submissions :) #elixirlang

#goatmire took conferences to the next level. The Presentations, the Speakers, the Attendees all were amazing. And It really showcased why I love the elixir community so much. Huge thanks to @lawik.bsky.social and the team for organizing such an awesome event

Cool!!! @maennchen.dev introduces Clarity! @ash-hq.org #elixirlang

#ElixirLang now runs the temporary parliament in Nepal

Well goatmire really has set a new standard for talks. Just wow! 🐐🐐🐐 #elixir

So goatmire has been entirely fantastic so far! It's a really cool event in the BEAM / @elixir-lang.org space! If you're not here you're missing out! If you are, come chat!

#Goatmire #Elixir Take 35% off all Elixir, Nerves and related titles Just use code Goatmire2025 (Only at Pragprog.com#Goatmire

Wow, this is amazing!!! 🔥 Elixir events not only about Elixir, but on Elixir! At @elixirconf.bsky.social EU they were using Elixir for streaming the talks. At @alchemyconf.com , they had an Elixir app to scan attendees' badges. Now at Goatmire, Elixir in the badges! #ElixirLang

Sweden’s first Elixir conference is here! 📍 Varberg 🗓️ 10–12 Sept Organized by the Underjord team — by Elixir enthusiasts, for Elixir enthusiasts. We’re glad to sponsor this community-driven event 💜 👉 goatmire.com#top #ElixirLang #BEAM

People are filtering into Varberg for #goatmire. The excitement is building. The Discord is hopping. People are reporting on their jet lag and seeing the town for the first time. #elixirlang

The Groxio team—Bruce Tate, Paulo Valim, and myself—are fresh off of a project where we helped scale an application and its development team all the way to launch. If your company could use #ElixirLang #Consulting help from one or more of us, let’s talk! groxio.com

On behalf of Piotr It is with great sadness that I inform of the passing of Piotr on July 29th, after his long fight with cancer. He was a great man, great engineer, a wonderful husband, father, brother and son. A dedicated Ruby community member. He will be sincerely missed Piotr's wife, Monika

Expert LS is out yall. #ElixirLang github.com/elixir-lang/...

OMG, Expert LSP is already an option inside Zed! 🎉🎉🎉 I thought I'd had to do some custom config to try it out, since it was announced just a few hours ago. Great work! #ElixirLang

Hi Bsky hivemind, is anyone looking for seasoned #ElixirLang developer? EMEA-based, fully remote. Either consulting or full-time.