Started the current client project to automate ops processes using LLMs. Ended up writing a compiler and linter along the way.
SWE is beautifully weird sometimes.
Same energy as: 'Code without comments, docs or tests is bug-free by definition'
Might give it an honest attempt in a couple of weeks. My current attention budget is more limited than Iβd like :)
Oh no, the urge to leave my current (Rust-based) SSG solution for the incremental compilation to possibly shave off time from my current 15ms full rebuilds instead of writing another blog post!
But seriously, font subsetting is a great feature to have.
It is only similar in terms of superficial syntax, a form of sum/product types and it having option and result types.
That may sound like a lot of overlap. It really isnβt. For starters, Gleam has no concept of traits, for example.
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 :)
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.
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.
Ε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.
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!
