I am fairly new to Go. I found out about the options pattern recently and applied it in a recent package I wrote. It definitely cleaned up the function signature imo

github.com/alabianca/id...

NaN === NaN // -> false 🤡

TIL! I’m too occupied with JS that I forget that CSS could be the answer

I’m in the same boat. I’m new to Bluesky and just learned last week about atproto lol. Was thinking of building something useless first to learn, like a graph view of your followers maybe with D3.js

Thing[]

Yep I agree. It forces you to think about errors.

Those are the top 3 use cases for sure. I also often end up using the ref to store references to library objects that are not aware of react’s lifecycle. For example when building a react wrapper library around a framework agnostic charting library for example.