3 ms·

And your Typescript CSS in JS thing using some new thing? TW is at least well documented and widely used and based on a fairly formalised bunch of classes that

And your Typescript CSS in JS thing using some new thing? TW is at least well documented and widely used and based on a fairly formalised bunch of classes that builds upon a concept that’s been used for 10+ years.

satvikpendem 4y ago
It's not my thing, I didn't make it, for one. Then just use CSS at that point, it's been here 20+ years then. I simply don't understand how it can be superior to regular CSS in any way simply because it maps one to one onto CSS properties anyway.
- NayamAmarshe 4y ago
  > I simply don't understand how it can be superior to regular CSS in any way simply because it maps one to one onto CSS properties anyway. Could just read the docs. https://tailwindcss.com/docs/utility-first https://tailwindcss.com/docs/utility-first
  - satvikpendem 4y ago
    I did, I even read Adam's initial post here on Hacker News itself. Just because they say it's better doesn't make it actually better. Indeed, to me, it is strictly worse.
    - NayamAmarshe 4y ago
      > Just because they say it's better doesn't make it actually better. They didn't say it's better. They said go ahead and use it first, before pulling out opinions. I perfectly understand your position, I've been there too but it's a complete 180 experience after you build just 1 project with it. It's a "won't go back" experience.
      - satvikpendem 4y ago
        I think you missed my previous comments saying how I've used it extensively the past few years for employers. It's like a bell curve, you like it and think, wow, this is amazing. Then as the years pass and you start having to maintain it, you steadily dislike it until you get to not wanting to use it anymore at all. The people who currently like Tailwind might simply not have gotten to this later stage yet.
        NayamAmarshe 4y ago
        > Then as the years pass and you start having to maintain it, you steadily dislike it > The people who currently like Tailwind might simply not have gotten to this later stage yet. And yet somehow the projects you were assigned did? I don't mean any disrespect, but I find it a bit questionable that any big project that uses Tailwind has had maintainability issues when Tailwind itself is pretty new to the scene. It'd be hard for you to prove this to be honest, while on the other hand, I could give you hundreds of thousands of testimonials countering your argument.
        satvikpendem 4y ago
        Hundreds of thousands of testimonials from companies using it in production and had been for the past few years and as not a new project? Sure, send me a list. I expect to see all of the hundreds of thousands of them on the list. My email is in my profile. It's anecdotal experiences at this point. As I said, I was using Tailwind from the beginning and loved it at first. Then the problems started.
- idkwhoiam 4y ago
  I do bare CSS for quick POCs but never on real projects. Vanilla JS & CSS sounds romantic when you solo but in a team setting it's better to use something we're all familiar with. At work we switched over from SCSS modules+global styles to Tailwind last year and it has been great so far: 1. No more custom CSS. No need to think how to name your classes. No more unused CSS. 2. Code completion (VSCode plugin for TW classes) 3. Well documented. Even our BE developers are able to jump in and do minor changes. The long CSS class name strings look funny but nobody complained about it in our team. Choose whatever works for your team. Tailwind has been nothing but a pleasure for us.
  - satvikpendem 4y ago
    Tell me how it goes in 5 years time because that's what I'm dealing with currently.

satvikpendem 4y ago

It's not my thing, I didn't make it, for one. Then just use CSS at that point, it's been here 20+ years then. I simply don't understand how it can be superior to regular CSS in any way simply because it maps one to one onto CSS properties anyway.

NayamAmarshe 4y ago
> I simply don't understand how it can be superior to regular CSS in any way simply because it maps one to one onto CSS properties anyway. Could just read the docs. https://tailwindcss.com/docs/utility-first https://tailwindcss.com/docs/utility-first
- satvikpendem 4y ago
  I did, I even read Adam's initial post here on Hacker News itself. Just because they say it's better doesn't make it actually better. Indeed, to me, it is strictly worse.
  - NayamAmarshe 4y ago
    > Just because they say it's better doesn't make it actually better. They didn't say it's better. They said go ahead and use it first, before pulling out opinions. I perfectly understand your position, I've been there too but it's a complete 180 experience after you build just 1 project with it. It's a "won't go back" experience.
    - satvikpendem 4y ago
      I think you missed my previous comments saying how I've used it extensively the past few years for employers. It's like a bell curve, you like it and think, wow, this is amazing. Then as the years pass and you start having to maintain it, you steadily dislike it until you get to not wanting to use it anymore at all. The people who currently like Tailwind might simply not have gotten to this later stage yet.
      - NayamAmarshe 4y ago
        > Then as the years pass and you start having to maintain it, you steadily dislike it > The people who currently like Tailwind might simply not have gotten to this later stage yet. And yet somehow the projects you were assigned did? I don't mean any disrespect, but I find it a bit questionable that any big project that uses Tailwind has had maintainability issues when Tailwind itself is pretty new to the scene. It'd be hard for you to prove this to be honest, while on the other hand, I could give you hundreds of thousands of testimonials countering your argument.
        satvikpendem 4y ago
        Hundreds of thousands of testimonials from companies using it in production and had been for the past few years and as not a new project? Sure, send me a list. I expect to see all of the hundreds of thousands of them on the list. My email is in my profile. It's anecdotal experiences at this point. As I said, I was using Tailwind from the beginning and loved it at first. Then the problems started.
idkwhoiam 4y ago
I do bare CSS for quick POCs but never on real projects. Vanilla JS & CSS sounds romantic when you solo but in a team setting it's better to use something we're all familiar with. At work we switched over from SCSS modules+global styles to Tailwind last year and it has been great so far: 1. No more custom CSS. No need to think how to name your classes. No more unused CSS. 2. Code completion (VSCode plugin for TW classes) 3. Well documented. Even our BE developers are able to jump in and do minor changes. The long CSS class name strings look funny but nobody complained about it in our team. Choose whatever works for your team. Tailwind has been nothing but a pleasure for us.
- satvikpendem 4y ago
  Tell me how it goes in 5 years time because that's what I'm dealing with currently.