Leon Qadirie

If we strive for consistency of `[Adjective]Supervisor` I’d vote for ElasticSupervisor. Dynamic if we aim to have very similar semantics as Elixir.

Otherwise Factory fits great, the baggage is there but makes it grokkable quite easily.
Slightly behind that, Generator.

I'm excited about this :)

From Rebar3 to Rebar4: Integrating with Erlang/OTP Building on top of Rebar3 to Fully Integrate with Erlang/OTP for All BEAM Languages, creating Rebar4 the next generation build tool.

Reminder to back rebar4 if possible, helping push the #erlang / #elixirlang / #gleam / #BEAM ecosystem.

www.kickstarter.com/projects/pee...

Such a cool idea!

Corresponding GitHub issue's TL;DR: fixed in `main`, better fix on the way.
github.com/elixir-lang/...

Our GitHub repository is now public!

github.com/elixir-lang/...

I keep getting surprised Thomas' work isn’t universally known in the community, but I am deep in the GenAI niche.

GitHub - thmsmlr/livebook_tools: Powertools for livebook.dev — AI Code Editing, MCP Servers, and Running Livebooks from the CLI Powertools for livebook.dev — AI Code Editing, MCP Servers, and Running Livebooks from the CLI - thmsmlr/livebook_tools

I heard good things about github.com/thmsmlr/live..., essentially facilitates editing the markdown via CLI-exposed (MCP?) interfaces.

That thread was made private by the mods.

Core takeaway is: @expert-lsp.org is actively worked on. Elixir LS currently benefits from public work on ElixirSense, but others are working on merging everything incl. these advancements. No timeline shared yet.

+1 for a critical assessment of repatch - the README and announcements sound *suspiciously* great 😅

Hyped for this; I juuust need to somehow reschedule the flight 😬

Only very vague ones that in the end might boil down to:
- will it compose well with other (unspecified) building blocks, and
- are there sufficient escape hatches/hooks to when it doesn’t

A reason I like Ash's Lifecycle model: hexdocs.pm/ash/actions....

Curious as in curious, not doubtful. :)

Curious how it feels in anger, but at first glance: this for sure is a beautiful interface!

Yes, really brought my productivity down a notch.

I need to improve my self-control.

Fortunately/unfortunately Goatmire is not sold out yet. I just goofed a bit on the backend.

Replace keyword with concrete keyword lists in specs by lukaszsamson · Pull Request #14611 · elixir-lang/elixir This PR: Replaces keyword/term with concrete keyword lists in specs for all functions taking options argument Adds missing documentation for some of the supported options Adds specs for functions ...

Łukasz Samson improving #ElixirLang keyword docs; laying groundwork for better autocomplete.

Also, @expert-lsp.org teasing… are we close to a better Elixir LSP era?

github.com/elixir-lang/...

Nice plan, incl. the long-term ’2.0’ considerations. :)

That is awesome! Predefined themes and/or easy way to define own themes?

Great either way!

For what’s it worth, I’m looking forward to explore Gleam's (new) OTP API and find out what its actual limitations are and what is just missing functionality OOTB.

It is a joy writing Gleam, and then I’m also really spoiled by the existing Elixir abstractions.

A case for inline type annotations Even better, here is the relatively small URI module from Elixir. Can you go through every function and type them according to your proposal? elixir/lib/elixir/lib/uri.ex at main · elixir-lang/elixir ...

I aspire to be as constructive as José is with #ElixirLang community feedback: elixirforum.com/t/a-case-for...

Thank you for that work; really cool stuff with peri as well!

No questions, just want to thank you for all the great work, you really are pushing the ecosystem forward a lot!

Enabling vim mode (or experimental helix mode) in addition to native key bindings and Zed’s own will go a long way, if you are open to that.

Not sure about being able to completely omit the mouse, though.

Clap is a joy to use. Bonus points for use cases where I can squeeze miette in.

Agreed, the book and approach of essentially just… having the full code ready and telling you what it does and why have a certain 'reference material vibe' to it, made some things click for me!

+1 here, I remember a (your?) talk about WASM Components at an Elixir Meetup in Berlin, very interesting topic indeed!

In Germany, it is known as ‘viking’s chess’. Fun indeed!

You folks are crushing it! :)

Any reason to not simply use #Gleam? Unlike 'Elixir' it is seldomly used in other contexts. Otherwise, I’d prefer #GleamLang as next-best option. :)

Looking forward to letting it cräsh.

Absolutely changed the way I prototype!