Yeah, Tailwind is great as long as you have some way to reuse markup, like React. You don't have to care about class names and whether CSS defined somewhere else affects styles of a current component at all. That last point makes sense for LLMs as well: all the styles that affect the current file are automatically in context since styling is local. Admittedly, there are other ways to achieve this but the ergonomics of Tailwind are just good. Having nice defaults and good training data is an added bonus.
The lack of single-file components is one of several reasons I wouldn't reach for React prior to the LLM craze[0]. For personal projects, I love Svelte. You wouldn't need tailwind there for the reasons proposed given their support for it.
[0] Things have probably changed, but Svelte 5 was a litmus test for how recent the data cutoff was for an LLM model. Meanwhile React _especially_ has no reason to change how the framework is used by coders. Thus there's years of scraped tutorials and sites for how to throttle a function or what-have-you in React.
I could probably find quite a lot of people who will tell you astrology is 80+% correct for them. Would you believe them or wait for an independent analysis? There are other AI "detector" systems out there that claim 99% accuracy. But independent research always found that they are actually garbage once used on real data. It's all in how you pick your tests. It's also funny to see how people on places like HN will easily dismiss stuff astrology, but fall for the exact same patterns when used in tech-y applications.
It's not really about the planets. It's about what other people believe about the planets.
You could work for a boss that's a Leo, and he/she believes only Leos deserve to get promoted, or that Leos and Scorpios should never be assigned together on a shared project. Your life and career trajectory under this boss could be totally different, depending on whether you were born a Leo or not.
Certainly "not all bosses" applies, but it's not really that farfetched or uncommon either. The point is that a correlation does exist, but it's a social one and not a physical or astronomical one (and it's also often a self-reinforcing/self-fulfilling one: Leos who read what astrology says Leos should do, may end up choosing to behave more like that).
So in the LLM example, it may not really matter much what physical markers of provenance or physical correlations there are, as social beliefs or perceptions about suspected provenance may be the strongest correlation anyways (in terms of impact and outcomes).
I just feel like, from the POV of AI companies, that reducing the amount of em dashes they use to "blend in" more and talk more human-like, for the sake of being less detectable, wouldn't be a big priority.
The problem seems to be deeper rooted. Cursor doesn't see cloning a repo with Cursor and code execution as separate security boundaries.
Cursor ships with Workspace Trust disabled by default [0]. A repo that includes .vscode/tasks.json with "runOn": "folderOpen" will already run arbitrary code [1].
reply