Hacker Newsnew | past | comments | ask | show | jobs | submit | listless's commentslogin

This makes sense from a business perspective. If your primary customers are men, you wanna branch out of that real quick. I think something like ~80% of all consumer spending in the US is done by women. You gotta go after that. That's an ENORMOUS market to just leave on the table.

That said, I fail to see how trying to attract more women alienated men. I just don't buy that culture war as a reason. I remember Nike doing some things that were a bit annoying that I wished they would just stay out of, but I still bought their shoes. The only thing more insufferable than the culture war is taking part in said culture war.


>I fail to see how trying to attract more women alienated men

It's less about Nike making decisions that men don't like and more about Nike spreading themselves too thin.

Just think about Nike as a company: the products they actually sell are generic, barely mid-tier clothes and athletic gear. Their actual product is their brand. That's why all of their products prominently display their iconic logo and everyone and their grandma knows their slogan is "Just do it."

A brand is only as valuable as the awareness of the brand. So every dollar that Nike spends on marketing is incredibly important for driving their bottom line. If you split those marketing dollars in an attempt to reach a new audience, you're necessarily spending less of those marketing dollars on the existing audience that found your brand valuable. So, in trying to attract more women, Nike ended up attracting less men.

The question, really, is how important is this dynamic. Apparently, it's pretty important. I don't think Nike made a blunder in attempting to expand their audience. I'm willing to bet that they started seeing some writing on the walls which suggested not doing anything was going to be bad enough that taking the risk to spread themselves thin was appropriate. But at the end of the day, I think modern consumerism moves too fast and is so much less concentrated than it was in the past (when Nike dominated) that they just couldn't keep everything together as effectively as they needed to.


I don’t agree. Building a date picker used to be next to impossible. Overnight it was trivial. That’s some serious disruption.

That was certainly not overnight. The biggest disruption they personally did was offering a better alternative to Bootstrap. More customization, JIT compilation that allowed for custom class interpretation without any added CSS, proper flex consideration, removing unused library classes in the production compilation step, etc.

Beyond this, you should really be thanking things like Shadcn for the “date picker disruption”. It is a component library which arguably could’ve existed without Tailwind ever existing.


why shadcn and not bootstrap? shadcn is like a cool weird approach to a ui kit but bootstrap got us a date picker iirc.

Nonsense. There have been perfectly good free date picker widgets available for every era of web development, going back to clunky server-rendered html templates.

Seriously. I always wonder who makes these comments, then I remember I'm old and there are people who don't remember every era of the web. Although, it's still incredibly weird to essentially claim that Tailwind solved date pickers.

You have to remember the biggest appeal of tailwind is that it throws away the entire cascade of css. The people that reach for it are choosing it because it offers less functionality, and is therefore simpler to reason about. I hesitate to say they don't understand css, I'm sure some of them do, but in my experience the devs that reach for it are the same who deride css and make statements such as "I have better things to do than learn css"

I think there's plenty of developers that are perfectly competent with CSS who still reach for Tailwind.

You're right that Tailwind throws away the cascade, or at least enables developers not to have to think about it (under the hood, Tailwind 4 uses pretty modern cascading features like layers), but people aren't reaching it because of a lack of understanding, they're reaching for it because as front-ends get increasingly componentized, the cascade becomes less and less of a benefit and more of an obstacle to be worked around, and something that gets that obstacle out of the way becomes more attractive.


I'm perfectly competent at CSS and... at this point I don't even look at CSS. I just feed descriptions of what I want to the LLM and it nails it every time. The result either looks the way I want or it doesn't.

I'm not universally pro-AI. I meticulously review every line of backend code, and still do hand edits. I review FE commits less carefully but still keep an eye on it to make sure AI doesn't go off the rails. But there's only so much trouble you can get into with CSS and the problems are the kind of bite-sized problems that LLMs excel at.

I don't think it matters at this point what you use for styling. If you like tailwind, the AIs use it just fine. If you like SASS, or raw CSS, the AIs are also just fine.

I'm not sure there's really a human job here anymore.


Do you store your CSS in separate common files independent of markup? Out of curiosity, do you run into issues with excessive token usage when you want to work with CSS?

That would be my gut instinct - you ask your agent to change a CSS rule, and your agent would feel the need to find all usage of that rule to avoid introducing unexpected changes. Does that happen? (I'm operating purely on assumptions here because I regularly use tailwind where changes are kinda definitionally local).


I'm quite versed in CSS but tailwind has convenient abstractions on top. It's like "why you need C if you have assembler". I don't remember when I wrote raw CSS last time. Even global styles I tend to express via @apply.

Don't forget that, in my opinion very positive way, it also normalized the concept of "uniform measurements". Every instance of `rounded-md` is the same on a site.

True. I'm grateful for that but typically reach for them via openprops or home built variables for most of my projects these days

IE, it has a built-in design system!

A bunch of people have already said this but I also have known CSS very well (being using it since its release) and even enjoyed it. Butt the moment I saw someone using Tailwind I thought, "I want that!" The idea that Tailwind is for, or rather only for, people who don't know CSS is very misguided. That said, I'm back to using vanilla CSS.

Indeed, I don't know what to make of such a bizarrely nonsensical assertion. Age and lack of experience doesn't really explain it, because all the poster needed to have done was make the simplest sort of web search. It's so wrong, it's... not even wrong.

> Thieves, grifters, rapists, pedos, just the absolute worst human garbage imaginable.

I would urge you strongly not to let yourself be this consumed by this kind of thinking. This is a distorted view of your fellow man - however accurate _some_ of it may be about _some_ people - regardless of their political affiliation. This kind of thinking is exactly how we got to where we are now and persisting in it will almost certainly get us more extreme reactions.

that said, the Republican establishment has proven itself unworthy of the office and should be shown the door in the next election cycle - in decimating fashion. So much so that it should cause a complete recalibration of that party.


>This kind of thinking is exactly how we got to where we are now and persisting in it will almost certainly get us more extreme reactions.

It was seeing a black guy, and then possibly a woman, and then possibly a black woman get to the top that got us where we are now. The message is clear, don’t disrupt up our image of the hierarchy, or else we will support the worst of the worst, as long as they maintain the order.


I take 1.25 every night. I titrated down off of three and ima keep going. I cannot tell the difference between those doses. Both make me very drowsy.


This is so good Ty.

Basically, looking at inflation over time, we look pretty good here.


Against what other metric? Income? Stock Market? Debt?


Oh man - hearing that we’re building MCP’s where there is no CLI makes me super nervous.

It’s one thing to dupe the functionality of your CLI for better agent integration. It’s another to make it the sole method of interface locking everyone into a spec that we may decide we can do better at some point. Then we gotta pay off all the MCP debt and it will be cheaper to just not.


I would agree here. And in my experience Qwen 27B and Deepseek v4 are also extremely good.

None of them are quite opus, but they are damned close and a no brainer if you care at all about cost.


This is the result of Elizabeth Warren blocking the merger with JetBlue.

I’m not saying it wasn’t the right thing to do. I don’t know. But this is definitely on her either way.


I felt pangs of emotion reading the post so it’s definitely not just you.

I think because GitHub has been such an important part of my life dating back to the very start of my career - just like you.

And it’s not just the technology, it’s the people. All the great projects there. The countless README’s I’ve dissected trying to setup something new. There’s people behind all of that and that always felt exceptionally meaningful to me.

It has been profoundly emotional to watch GitHub degrade over the past year. It’s almost like watching someone you love slip away. Which I have also done. It’s not the same, but there is something familiar in the pain.

Meanwhile streamers dunk on it in YouTube videos and on X and none of it is funny to me. It’s just tragic.

Now I’m choked up. Dammit all to hell.


I agree. And even on Ubuntu, the performance vs same specs on Windows is ridiculously better.

Apps are still a huge gap on Linux, but as an OS, I choose it every time over Windows and MacOS.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: