- #93
- #92
- #91
- #90
- #89
- #88
- #87
- #86
- #85
- #84
- #83
- #82
- #81
- #80
- #79
- #78
- #77
- #76
- #75
- #74
- #73
- #72
- #71
- #70
- #69
- #68
- #67
- #66
- #65
- #64
- #63
- #62
- #61
- #60
- #59
- #58
- #57
- #56
- #55
- #54
- #53
- #52
- #51
- #50
- #49
- #48
- #47
- #46
- #45
- #44
- #43
- #42
- #41
- #40
- #39
Is it necessary to learn Sass in 2024?
Recently, there was a discussion about whether it is possible to introduce Sass to solve some existing problems, and my response was negative:
- Early CSS features were immature, which necessitated support from Sass (nested selectors, variables, calc, etc.)
- The additional translation step increases the complexity of the development environment and the cost of learning and maintenance
- Vendor lock-in
For me, Sass is like CoffeeScript to JavaScript; when the native ecosystem matures, there is no need to use it. Every technology arises to solve underlying problems, and before using additional tools to address issues, one should often ask themselves why they are making such a choice and whether the trade-offs are reasonable.
- #38
- #37
- #36
- #35
- #34
- #33
- #32
- #31
- #30
- #29
- #28
- #27
- #26
- #25
- #24
- #23
- #22
- #21
- #20
- #19
- #18
- #17
- #16
- #15
- #14
- #13
- #12
- #11
- #10
- #9
- #8
- #7
- #6
- #5
- #4
- #3
- #2
- #1