A blog about modern PHP, the web, and programming in general. Follow my newsletter and YouTube channel as well.

Stitcher Engineering Blog offers insights, tutorials, and updates on building scalable, reliable, and high-performance systems for podcasting and audio streaming. Covering topics such as backend architecture, media processing, and content delivery, Stitcher Engineering Blog provides resources for developers and engineers working in the audio streaming industry. Developers can learn about building resilient systems, optimizing media workflows, and delivering high-quality audio experiences through Stitcher's blog posts and technical articles.

stitcher.io

A developer reflects on becoming so dependent on Tailwind CSS that they've lost fluency in vanilla CSS. The article explores how Tailwind's naming conventions don't map one-to-one with CSS properties, creating a form of vendor lock-in where switching back to pure CSS feels foreign. The author appreciates Tailwind's component-based approach for keeping styles contained but wishes for a solution that maintains this workflow while using standard CSS syntax.

Vendor locked

Ok but that’s not what vendor locked means

I’m not sure that word means what you think it means.

After using Tailwind for an year. I would agree with this.
Switching back and forth between tailwind and css seems a bit hactic