Lets start collecting some best practices and tips for optimizing applications

[UncleGrumpy]

Making the transition from server to the constrained memory footprint and slower processor cores that AtomVM is designed to run on can be a jarring transition. It can be equally difficult for MCU firmware developers just learning about the BEAM to understand the memory usage usage of different methods available to them in the BEAM ecosystem.

We should start collecting best practices tips, and approaches to keep memory (and cpu) usage as efficient as possible. We should also collect pattern that should be avoided and pitfalls to watch out for. The suggestions collected here can serve as a starting point for expanding the "Programmers Guide", which would be a valuable addition to our documentation.

[pguyot]

One approach could be to start from Erlang's efficiency guide and see what applies and what doesn't apply to AtomVM.
A lot of https://www.erlang.org/doc/system/binaryhandling.html#how-binaries-are-implemented applies especially heap binaries vs refc binaries.

We should also stress the cost of lists as opposed to binaries and tuples, maybe with some dos and don'ts.

Finally, conversation with @robinchew hihglighted we should explain the cost of SSL connections.