3 ms·
Never preferred tailwind. Much simpler to write plain css. It’s easier to create reusable components than what ppl think. CSS hardly has a steep learning curve.
by potato-peeler 26d ago
Never preferred tailwind. Much simpler to write plain css. It’s easier to create reusable components than what ppl think. CSS hardly has a steep learning curve. Problem with tailwind and many newer css frameworks I see posted even on HN, is they don’t seem to work on older devices, which is a shame. I guess ppl simply test on their latest phones and call it a day. Older ios itself have roughly 7% market share [1], that’s millions of devices that can’t access the web properly.
[1] - https://www.statista.com/statistics/1118859/mobile-apple-ios-version-share-in-the-us/ https://www.statista.com/statistics/1118859/mobile-apple-ios...
- lemonberry 26d agoWhy wouldn't Tailwind work on older devices? It's just a bunch of classes. If you're using a feature the browser doesn't support it's not going to work whether it's vanilla css or tailwindcss. That said, I prefer vanilla CSS. Modern CSS is great.
- potato-peeler 26d agoHere is the tailwind website itself - https://ibb.co/album/kHqGx8 https://ibb.co/album/kHqGx8 This is on iOS 13.6 I have no idea why tailwind needs or does something which makes it utterly unusable. I miss the days when many websites used to offer simple html versions of their apps, like gmail (https://techcrunch.com/2024/02/22/google-is-killing-gmails-basic-html-view-in-2024/ https://techcrunch.com/2024/02/22/google-is-killing-gmails-b...)
- deleted 26d ago[deleted]