Spoilers! Like with so many things, the answer is “it depends.” How come? Tailwind and BEM are two approaches to writing and maintaining CSS. Comparing them is a bit like comparing apples and oranges, in that while they’re separate, they’re still fruit. This is to say that having an approach to manage your CSS—like any other code—is a good thing.
This is yet another thing where you have to inform the browser about your site so that it can Do Performance Good™. It is information that it can figure out by itself, but not until it has done things that have a performance cost. So you have to tell it up front, allowing it to avoid doing certain types of work.
I sometimes have a third reason to use CSS grid: prevent layout shifts. I tried to find a fancy acronym for this technique but all I got was ALSGST: “Anti Layout Shift Grid Stacking Technique”. I guess I won’t be receiving many skill endorsements for “coining tech terms” on my LinkedIn profile so you better send me some suggestions.
In this article, we will go through the different possibilities to store data in the browser. We will cover three use cases for each method to grasp the pros and cons. In the end, you will be able to decide what storage is the best fit for your use case. So let’s start!
End-to-end testing is becoming a more popular way for developers to test their apps across complex operations, UI states, mobile responsive views, and more. But how do you test your applications for visual integrity? How can you know with complete confidence that you haven’t introduced a visual regression?