As we build a messaging platform, messages need to be editable, but changes need to be understood. Having a very basic "history" view seems easier to build, even if it's with a simple diff algo like this.
"Problem: Current masonry solutions lack performance, and are bloated with unnecessary features"
"Solution: Bricks capitalizes on batched reading of layout properties for blazing fast packing time, no matter how many items."
Even years into my career as a front-end developer, I still run into new projects were I need to evaluate what the best approach to CSS is. There's no one-size-fits-all and if anyone tells you there is, they're oblivious.