From f34ac97b0d78542fd52376b1254068437d8ba457 Mon Sep 17 00:00:00 2001 From: bmsuseluda Date: Tue, 26 Apr 2022 11:05:30 +0200 Subject: [PATCH] Update radar/2022-03-28/sass.md Co-authored-by: resah <3407199+resah@users.noreply.github.com> --- radar/2022-03-28/sass.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/radar/2022-03-28/sass.md b/radar/2022-03-28/sass.md index 3dcdee4..6d22631 100644 --- a/radar/2022-03-28/sass.md +++ b/radar/2022-03-28/sass.md @@ -6,7 +6,7 @@ featured: false --- Since the heydays of Sass, the requirements for styling solutions have changed. -With modern solutions like [CSS-in-JS](/methods-and-patterns/css-in-js.html), [Tailwind](/languages-and-frameworks/tailwindcss.html) or [PostCSS](/tools/postcss.html), you get scoped css out of the box and can get rid of the manual and therefore error-prone BEM methodology. +With modern solutions like [CSS-in-JS](/methods-and-patterns/css-in-js.html), [Tailwind](/languages-and-frameworks/tailwindcss.html) or [PostCSS](/tools/postcss.html), you get scoped CSS out of the box and can get rid of the manual and therefore error-prone BEM methodology. Furthermore, mapping class names to elements is no longer necessary. In general the modern solutions bring a better and more robust developer experience. Therefore we put Sass on hold.