4 ms·

I'm not a fan of tailwind, but this isn't what I optimise for when building websites. Besides, I suspect (but not know, because my experience with tailwind is

I'm not a fan of tailwind, but this isn't what I optimise for when building websites. Besides, I suspect (but not know, because my experience with tailwind is very minimal) that that output is readable and understandable by those experienced and developing with tailwind. On top of all the other affordances modern dev tools gives to understand styling on elements (esp. the computed pane)

barnabee 3y ago
When you build websites you are creating code for others to read as much as you're creating an "app" or document. It's the very essence of what's good and special about the web. If the companies that are trying to do away with this succeed, we will have lost something important. The web is and should remain de facto open source.
- madeofpalk 3y ago
  > When you build websites you are creating code for others to read as much as you're creating an "app" or document. I couldn't disagree any more with this. When the overwhelming majority of your users would never actually be impacted by this, I believe you have more of a responsibility to the bulk of your users, rather than a fraction of a percentage. I say this as an open-source developer, who ships source maps to production. I would much rather us increase our development veloticity and build higher quality products rather than satisfy one nerd who might want to occasionally view source.
  - rado 3y ago
    Bloat is detrimental to the bulk of your users.
    - deleted 3y ago
      [deleted]
- haswell 3y ago
  > When you build websites you are creating code for others to read as much as you're creating an "app" or document. That's an approach people are certainly welcome to take, and I'm glad that some people do, but I disagree that this is what the act of building a website entails. This feels a bit like romanticizing the early days of the web, when the primary form of learning involved reading other people's source code. The depth and breadth of ways to learn in 2024 looks nothing like those early days. If I choose to build something to solve a particular need or to communicate something I care about, it's my choice as to how I do that. > It's the very essence of what's good and special about the web. The very essence of what's good and special about the web is the diversity of solutions, the myriad of entry points to becoming a web developer, the existence of tools ranging from vanilla HTML/CSS all the way up to complex frameworks like Tailwind, and your freedom to pick your path. Tailwind's existence does not threaten the layers underneath it.
leptons 3y ago
I work on a "white label" site that gets customized by an army of css coders/designers. Tailwind seems like it would be a total non-starter for us.
- mm263 3y ago
  Your use case is fairly specific. Tailwind is a tool, if it doesn't make sense to you and your use case, it's okay to not use it. That said, it's not okay to misrepresent what Tailwind actually is like the original commenter did.

barnabee 3y ago

When you build websites you are creating code for others to read as much as you're creating an "app" or document. It's the very essence of what's good and special about the web. If the companies that are trying to do away with this succeed, we will have lost something important. The web is and should remain de facto open source.

madeofpalk 3y ago
> When you build websites you are creating code for others to read as much as you're creating an "app" or document. I couldn't disagree any more with this. When the overwhelming majority of your users would never actually be impacted by this, I believe you have more of a responsibility to the bulk of your users, rather than a fraction of a percentage. I say this as an open-source developer, who ships source maps to production. I would much rather us increase our development veloticity and build higher quality products rather than satisfy one nerd who might want to occasionally view source.
- rado 3y ago
  Bloat is detrimental to the bulk of your users.
  - deleted 3y ago
    [deleted]
haswell 3y ago
> When you build websites you are creating code for others to read as much as you're creating an "app" or document. That's an approach people are certainly welcome to take, and I'm glad that some people do, but I disagree that this is what the act of building a website entails. This feels a bit like romanticizing the early days of the web, when the primary form of learning involved reading other people's source code. The depth and breadth of ways to learn in 2024 looks nothing like those early days. If I choose to build something to solve a particular need or to communicate something I care about, it's my choice as to how I do that. > It's the very essence of what's good and special about the web. The very essence of what's good and special about the web is the diversity of solutions, the myriad of entry points to becoming a web developer, the existence of tools ranging from vanilla HTML/CSS all the way up to complex frameworks like Tailwind, and your freedom to pick your path. Tailwind's existence does not threaten the layers underneath it.

leptons 3y ago

I work on a "white label" site that gets customized by an army of css coders/designers. Tailwind seems like it would be a total non-starter for us.

mm263 3y ago
Your use case is fairly specific. Tailwind is a tool, if it doesn't make sense to you and your use case, it's okay to not use it. That said, it's not okay to misrepresent what Tailwind actually is like the original commenter did.