I don’t know why you think I haven’t mentioned it’s advantages at all or is trying to paint me as not wanting to acknowledge “plainly obvious advantages”. I literally said that Tailwind is the industry’s current answer to working with CSS in a way that seems to work with the current and modern economic pressures. I have literally mentioned in my other comment that its advantage is that it’s as an easier to learn, easier to collab tool. Idk what else I’m supposed to say.
You were asked to say the benefits of Tailwind, but instead of saying what the clear benefits are, you are the one who chose to answer by saying that “many industry experts use it”. I thought it was a ridiculous reply, and so I chose to be ridiculous to draw parallels of your logic to justifying for the existence of fossil fuel companies. If you do not understand the concept of similies and hyperbole, I’m sorry I can’t help you there.
And you seem to fail to see the bigger picture of things and simply treated my other comment as a “I claim that this is the right way to go”. I do not claim that it is one, and is merely lamenting on the fact that there was, and emphasis here to help you read, what I think was a better way. If you’re going by the metric that economies are efficient if only things can be made quickly, then my comment is pointing out that you are simply trapped by dogma, and is merely being a part to toxic capitalism where it’s a rat race to the bottom of the barrel.
If you think CSS with the C is “slowing down development and is increasing complexity as well as potential for bugs and side effects”, then you are part of the problem. And no, I do not agree that people have “tried to embrace the cascade for a long, long, long time”. What I see instead is that they have simply lived with it because we haven’t gotten to a point where we write SS without the C. Seriously, I still don’t understand that if virtually an entire industry just hates the cascade so much, why haven’t y’all just removed it?
I’m not sure if my message is getting across to you, because it seems like you are very much happy with the state of things and the direction it’s going at. And you don’t have to spend your energy talking to someone who’s clearly on the minority and losing side of the industry. I’m just some person who happens to like CSS with the C, and enjoy writing CSS so much as it allows me to so concisely describe what I want across an entire application, and is simply lamenting on the fact that we haven’t did much to improve literacy of CSS, thinking that better CSS literacy translates to better engineers. So save your breath and energy pal.
I don’t know why you think I haven’t mentioned it’s advantages at all or is trying to paint me as not wanting to acknowledge “plainly obvious advantages”. I literally said that Tailwind is the industry’s current answer to working with CSS in a way that seems to work with the current and modern economic pressures. I have literally mentioned in my other comment that its advantage is that it’s as an easier to learn, easier to collab tool. Idk what else I’m supposed to say.
You were asked to say the benefits of Tailwind, but instead of saying what the clear benefits are, you are the one who chose to answer by saying that “many industry experts use it”. I thought it was a ridiculous reply, and so I chose to be ridiculous to draw parallels of your logic to justifying for the existence of fossil fuel companies. If you do not understand the concept of similies and hyperbole, I’m sorry I can’t help you there.
And you seem to fail to see the bigger picture of things and simply treated my other comment as a “I claim that this is the right way to go”. I do not claim that it is one, and is merely lamenting on the fact that there was, and emphasis here to help you read, what I think was a better way. If you’re going by the metric that economies are efficient if only things can be made quickly, then my comment is pointing out that you are simply trapped by dogma, and is merely being a part to toxic capitalism where it’s a rat race to the bottom of the barrel.
If you think CSS with the C is “slowing down development and is increasing complexity as well as potential for bugs and side effects”, then you are part of the problem. And no, I do not agree that people have “tried to embrace the cascade for a long, long, long time”. What I see instead is that they have simply lived with it because we haven’t gotten to a point where we write SS without the C. Seriously, I still don’t understand that if virtually an entire industry just hates the cascade so much, why haven’t y’all just removed it?
I’m not sure if my message is getting across to you, because it seems like you are very much happy with the state of things and the direction it’s going at. And you don’t have to spend your energy talking to someone who’s clearly on the minority and losing side of the industry. I’m just some person who happens to like CSS with the C, and enjoy writing CSS so much as it allows me to so concisely describe what I want across an entire application, and is simply lamenting on the fact that we haven’t did much to improve literacy of CSS, thinking that better CSS literacy translates to better engineers. So save your breath and energy pal.