Tailwind has taken the world by storm because it let's engineers completely ignore actually learning the technology that powers the web. That doesn't make it good - and it isn't. It's a bloated mess with tons of random technology surrounding the ecosystem in an attempt to make it usable.
Tailwind literally only becomes usable for large scale applications once you have combined base tailwind, postcss, a number of tailwind plugins, custom themes, tailwind-variants, tailwind-merge, clsx/classnames, some custom written typescript typing tools, and a number of editor and linter plugins.
People here saying "It works well with AI" is such a wild take for so many reasons, not least of which is just straight up admitting that you don't mind your code being unreadable garbage because you aren't reading it anyway.
The `@apply` syntax glazing here is wild too - you're literally just writing CSS at that point. Just use vanilla CSS. Like that is all this is:
```css
.select2-dropdown {
@apply rounded-b-lg shadow-md;
}
.select2-search {
@apply rounded border border-gray-300;
}
.select2-results__group {
@apply text-lg font-bold text-gray-900;
}
```
The only "good" thing about tailwind is that right now the rest of the ecosystem is woefully lacking for a number of reasons and tailwind has the benefit of being used by a ton of random projects so you can find tools and references to make it better. But it's not good.
The idea that Tailwind prevents you from learning CSS has always been very silly because Tailwind is CSS. You cannot learn Tailwind without learning a lot of CSS. The Tailwind docs are the most concise and practical CSS docs around.
Web technologies succeed when they let people not have to understand things. React is the same as tailwind: it captures the box model experts already used to reason about web pages and made it literal.
As long as the job of "web developer" is about assembly-line delivery of features, it will continue to be strategic to choose tools that are worse for experts and better for amateurs.
Company acquired us in late 2022, then cut the acquired product and team in late 2023. Similar to others here, I've been applying left and right, but only hearing back on every 10 or so jobs.
Some numbers from December:
- 26 jobs applied to
- 14 just never replied
- 4 sent standard "we're looking for other candidates" emails
- 5 went to different stages of interviews only to resolve into "offer made to another candidate"
- 1 filled all the positions they had, but left the interview "open" for when new positions open up
- 1 is hopefully pending me getting an offer this week
Of the 5 that went with other candidates:
- 1 went all the way to right before the offer and they basically told me the had to decide between me and another candidate and the other candidate had direct experience with a product they wanted to build in early 2024
- 1 was supposed to really kick off after the holidays, told me waiting until after the holiday was what the preferred. Emailed me today to tell me they had a candidate accept an offer and my interviews would be cancelled.
Honestly feel like it should be a legal requirement to inform a candidate if you have an active offer out for the position they are applying to.
Been using Multiverse for a bit now and I honestly love it so very much. It's a brilliant mix of creative expression and creative limits - I can make cool stuff without having the infinite array of options that I would in design software. I recently wrote about my experience with old forums when I was a youngling on the internet and creating the post was honestly so much fun! I've felt my creativity really coming back since I've started using Multiverse.
You're ignoring a major component - Warehouse jobs are likely location-dependent and switching incurs other, not obvious costs. Targeting all of capitalism is a good idea, but one that is pretty hard to change.
Tailwind literally only becomes usable for large scale applications once you have combined base tailwind, postcss, a number of tailwind plugins, custom themes, tailwind-variants, tailwind-merge, clsx/classnames, some custom written typescript typing tools, and a number of editor and linter plugins.
People here saying "It works well with AI" is such a wild take for so many reasons, not least of which is just straight up admitting that you don't mind your code being unreadable garbage because you aren't reading it anyway.
The `@apply` syntax glazing here is wild too - you're literally just writing CSS at that point. Just use vanilla CSS. Like that is all this is: ```css .select2-dropdown { @apply rounded-b-lg shadow-md; } .select2-search { @apply rounded border border-gray-300; } .select2-results__group { @apply text-lg font-bold text-gray-900; } ```
The only "good" thing about tailwind is that right now the rest of the ecosystem is woefully lacking for a number of reasons and tailwind has the benefit of being used by a ton of random projects so you can find tools and references to make it better. But it's not good.