AJR/TechradarDev
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update radar/2022-03-28/sass.md

Browse Source 
Co-authored-by: resah <3407199+resah@users.noreply.github.com>
This commit is contained in:
bmsuseluda
2022-04-26 11:05:30 +02:00
committed by GitHub
parent 695c7c15eb
commit f34ac97b0d
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
radar/2022-03-28/sass.md
View File

@@ -6,7 +6,7 @@ featured: false
--- ---
Since the heydays of Sass, the requirements for styling solutions have changed. 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. 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. In general the modern solutions bring a better and more robust developer experience. Therefore we put Sass on hold.