uuid: - value: 42904e0f-f6d7-496e-8bce-72bd1e669e99 langcode: - value: en type: - target_id: daily_email target_type: node_type target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7 revision_timestamp: - value: '2025-05-11T09:00:12+00:00' revision_uid: - target_type: user target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849 revision_log: { } status: - value: true uid: - target_type: user target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849 title: - value: 'Why do you still write Sass?' created: - value: '2024-05-27T00:00:00+00:00' changed: - value: '2025-05-11T09:00:12+00:00' promote: - value: false sticky: - value: false default_langcode: - value: true revision_translation_affected: - value: true path: - alias: /daily/2024/05/27/why-do-you-still-write-sass langcode: en body: - value: |

Yesterday, I asked if it's time to stop writing Sass.

If you still use Sass and are writing new styles with Sass, I'd like to know why.

Reply to this email and let me know.

I'm working on a project and migrating from the existing Sass styles to Tailwind CSS-generated utility classes, but with CSS custom properties (variables) and other Sass-like features now supported by browsers, writing vanilla CSS again is an interesting option.

format: full_html processed: |

Yesterday, I asked if it's time to stop writing Sass.

If you still use Sass and are writing new styles with Sass, I'd like to know why.

Reply to this email and let me know.

I'm working on a project and migrating from the existing Sass styles to Tailwind CSS-generated utility classes, but with CSS custom properties (variables) and other Sass-like features now supported by browsers, writing vanilla CSS again is an interesting option.

summary: null field_daily_email_cta: { }