@shooboo Makes sense! And damn, I guess I want to learn Erlang now.
#elixir programmer <> late thirties <> she/they <> #matrix and Spritely enthusiast
Banner and PFP by Cesya Palmer.
Would an OCapN implementation in #Elixir essentially be an implementation in Erlang?
@liberty This practice is new to me and looks really cool. Thanks for posting about it!
@uhoreg Thanks! I'm excited to finally give it a shot.
OK, I've picked up enough essential Guile Scheme to feel comfortable trying to hack with Spritely Goblins now.
Aiming towards a web app that allows tracking shared expenses. Starting with the Guile part, wrapping it all in an event loop, and compiling it to wasm with Hoot. Then write up the UI shell...haven't decided with what yet, but leaning towards either React with Typescript or Gleam? Should probably keep it simple.
Then...then I see if I can extend it to be a p2p application.
@CactuarJoe I once played against a really nice Yedora deck with that premise, actually! They won with a combo involving [[Temur Charger]], a sac outlet, and [[Altar of the Brood]]. It's a fun idea to explore, imo!
Today's learning exercise is Guile Hoot!
I have to admit that a lot of this article went over my head, but the core concept of #WebAssembly being a fundamental abstraction was interesting to read.
https://wingolog.org/archives/2024/01/08/missing-the-point-of-webassembly
@jv For me, it's mostly smartparens and rainbow-delimiters. I also turn strict mode on for smartparens and mapped going forward and backward by an s-expression to a couple of convenient keys. I'm pretty sure the default scheme-mode handles intelligent indentation, which is how I learned to love Scheme.
I have to say, I hated the syntax of #Scheme at first. It just wasn't aesthetically pleasing to me. But with the right editor tooling, I don't even notice the parentheses anymore.
Got an idea for an #Elixir macro. For my fellow alchemists, does the following look like syntax that makes sense to you?
with_branching {:ok, result} <- {:ok, result},
:noninteractive <- interactive?(),
:never_reached <- never_invoked() do
IO.puts("Never reached")
branch
:interactive ->
IO.puts("First puts")
:ok <- :error
:other_branch ->
IO.puts("Never taken")
else
:error ->
IO.puts("Second puts)
end
@stevestreza @sarahstreza From a fellow trans Sarah with a different spelling, congrats!
But at home, oh, at home, I'm an artisan, sourcing ingredients from the finest places. At home, my passion for the craft is alive again.
Part of it was fully embracing the difference between the craft of software and the production of it. Most industries don't need craft, they need plug and play products that are fully disposable with minimal disruption. At work, I'm an expensive line cook slamming out frozen burger patties for drive thru customers at one of dozens of McData Fast Food.
I feel like I've rediscovered my passion for my field. I feel like I've been sitting down for so long that I forgot what standing is like, and now I'm standing again.
@ericsfraga Too true!
@wiersdorf Just wanted to follow up to say thanks so much for your kit! I ended up going in a pretty divergent direction, but it was the perfect foundation to play with. I'm already into such a groove with emacs that going back to vscode at work is tripping me up, lol.
@art_codesmith Go for it! I just started my #emacs journey in earnest over the weekend and it's been so fruitful for me. I also looked into Doom but got overwhelmed. Have you seen Bedrock? (https://fosstodon.org/@wiersdorf/117338742370015746) I ended up going in a pretty divergent direction with my config, but this was such a great starting place.
Irregular reminder that people who are #ActuallyPsychotic are much more likely to suffer physical violence than perpetuate it. I assure you that living through psychosis is a terrifying experience even without violence on either side.