Assuming GitHub, if the squashed commit links to the PR, that incremental history is still easily accessible to someone who wants to understand how a change came about. For someone just keeping up with a project, one commit per feature on main is much friendlier.
How does it feel if it has a small background on top of the text, but the whole button only appears if you're hovering the code element?
Here's a better thread on it with reasoning from José and others!
elixirforum.com/t/possible-p...
For sure! I've been thinking a bit about possible terminal APIs that gracefully degrade when raw mode isn't available, but are nice and snappy when it is. I don't want to have to wait for broad OTP 28 usage!
Played around with OTP 28's "raw mode" to make a snappy terminal-based chat app. Thanks @zachallaun.com for the heads-up about this upcoming feature! Demo video in the README
#ElixirLang
github.com/spencerolson...
If you're working on an HTML component library, consider an HTML structure that makes the little gap between checkbox and label clickable!
Makes sense. My inclination would be to vendor it in, but perhaps that's solving a problem that isn't really there if everyone using LVN in anger is fine using OTP 27 anyways.
Would it be feasible to vendor in :json as :lvn_json (or whatever)?
Gifs don't work, but video does!
I... uh... I think Bluesky might not support gifs...?
Elixir demo showing raw and cooked mode terminal input.
Let's try it one more time...
Bluesky question... ^ this is supposed to be a gif, but it's just a static thumbnail for me. Does it play for anyone else?
Terminal raw mode coming to #ElixirLang with OTP 28! Pretty excited about this.
What is this... outside... you speak of...
Agreed, been my go-to for the last couple months.
Out of curiosity, do you think it's the `dynamic(...)` or the `false or {term(), binary()}` part that's difficult to grok?
I ask because I wonder if they will become simpler to understand as inference improves and we see fewer dynamic types.
I wonder if you could stick "restore to a reasonable default" ANSI codes at the front of your prompt to ensure things are always in an expected state after running a command!
👋
Yep, I'm going to just let today suck. Can work on myself and my reaction to all this tomorrow.
Writing an Igniter installer for your #ElixirLang library?
I'd definitely recommend giving Mneme and mix mneme.watch a try for instant feedback on what your installer is doing.
hexdocs.pm/mneme/readme...
Agreed! This would also address what I perceive to be the biggest complaint about Phoenix docs: not knowing which package to search for docs in. While I really appreciate AshHQ pulling everything together, I've occasionally wished it were just hexdocs because it's so familiar at this point!
