5 ms·
Tailwind gives you inline media queries and the confidence that your css doesn’t impact other elements on your site. Also you don’t need to think up class names
by jjdeveloper 5y ago
Tailwind gives you inline media queries and the confidence that your css doesn’t impact other elements on your site. Also you don’t need to think up class names.
CSS variables are great, I just don’t really understand the value, I guess it gives you a bit of constraints for consistent styling.
- spankalee 5y agoTailwind doesn't let you use selectors and co-locate style definitions. It's effectively shorthand for inline styles. Pollen lets you use nicely defined values like Tailwind, but use CSS as designed to assemble them into sets.
- weird-eye-issue 5y agoYou can do the same with Tailwind by using @extend
- Tomte 5y agoIf you use the whole node-based toolchain. This looks fantastic, because I don't need any of that.
- weird-eye-issue 5y agoYeah but for most production apps it's just one extra thing to add to Webpack so isn't really an issue
- Tomte 5y agoYou've managed to sweep away "some people don't use node.js" with "but other people" —presumably you— "use it". That's not even an argument.
- weird-eye-issue 5y agoSorry it's hard to follow your incoherent comment with random mismatched quotes. I wasn't trying to make an argument, just an observation that including the Tailwind build process in most modern apps is not a big deal. If it doesn't work for you that's fine, I'm not trying to "argue" with you
- deleted 5y ago[deleted]
- weird-eye-issue 5y agoBy the way I like how you replied telling me to go away, got downvoted (by somebody else), deleted your comment, and then flagged my comment
- spankalee 5y ago@extend isn't CSS though
- di4na 5y agoThat could be solved if someone took it to shepherd it through the process. And honestly we need it.
- rahimnathwani 5y agoWith tailwind, it's sort of assumed that you're using e.g. React components. So all buttons will look the same because you'll import the button component, that's defined in a separate style. Pollen seems to me closer to bootstrap: define classes for each thing, and then use them everywhere. If you're designing a page or site without breaking your HTML into separate components, I can see the point of Pollen. (I am not a front-end expert, and my opinion is based on my limited experience using bootstrap, tailwind and tailwindui+react.)
- scns 5y agoTailwind is in not coupled to React, Adam Wathan its' creator used Laravel when he made it.
- rahimnathwani 5y agoIf you're going to use Tailwind with Laravel, you're going to break your pages up into Blade Components to keep things consistent, right?
- scns 5y agoYep, but they are called templates in backend frameworks, You write HTML with sprinkled in logic in Elixir/PHP/Python/Ruby etc. Components is the terminus used in (usually) JavaScript frontend development where you write JS logic and HTML is only used in the render/view/etc function.
- rahimnathwani 5y agoEven backend frameworks distinguish between templates and components. For example, Laravel has Blade templates and Blade components. From the documentation on the latter: "Components and slots provide similar benefits to sections, layouts, and includes" If you use Tailwind with Blade templates, but don't use {components, sections, layouts, includes}, then you'll have a hard time keeping things consistent. Because you'll define how a button looks over and over in each template. In that case, something like Bootstrap or Pollen would be easier. But the right way is probably to break your templates into smaller pieces (e.g. components) so you can use Tailwind but still share things like buttons between templates.