For what it’s worth:

2.0.0 should be much more mature and performant. I’m aiming to ship it by the end of the month.

I know the warnings in 1.3.0 might be annoying, but I didn’t really have another choice. 😞

is there a way in Gleam to compile some modules only for JS and others only for Erlang,
so I can get rid of this extremely annoying warning?

Wow, I finally took a proper look at string_width and… damn.
Really impressive work...
I genuinely re-learned a bunch of things reading it.

Those Unicode mines are a terrible place 😅

I was already halfway through reinventing the wheel, so I might as well finish my thing in pure Gleam and see how much sanity I have left.

Also: that library rules.

"All glory to the string_width library!" - Futurama 🚀

Nope 👀

Maybe you just saved me 😄

Fair point!
For extra context:
he’s a Model Checking / Formal Verification researcher, but new to FP.
So the challenge is twofold: coming from C and learning FP, while also understanding OCaml’s module system (signatures, functors as dependency injection, etc.).

This resonates a lot! I’ve never been linear, and trying to publish only “finished” ideas hurt more than it helped.
Your digital garden framing clicks, doing things as they come, letting them mutate. I’ve always called that being punk: messy, weird, alive, unpolished, unpredictable a bit näif ☺️

Thank U so much!

Well, Gleam deserves this. It rocks!

woah! you linked me all the superstars! 🤩

The only time I used PHP was so long ago…
that the only thing I remember
is my hosting provider shutting the service down for violating the TOS 😂

oh gosh. Is php still alive? ( obviously I'm joking )