I’m so tired of reading LLM slop articles. I don’t mind someone using AI assistance but it should be embarrassing to put your name next to something you so obviously didn’t write. I don’t remember who said it but I really like this summary: posting LLM slop as your own writing destroys the reader/writer contract. Normally you’d expect the writer to have spent more effort on a piece than the reader. But now the reader…
CSS-in-JS: The Great Betrayal of Front End Sanity
11–17 of 17 posts
Re: CSS-in-JS: The Great Betrayal of Front End Sanity
#12> We’re entering a new chapter where simplicity is sophistication again, where global stylesheets coexist peacefully with scoped rules. does anyone know, scoped style rules are here to stay or not? is deprecated and in HTML spec is not allowed in body https://html.spec.whatwg.org/multipage/semantics.html#the-st... (This is how I suspect it's LLM slop, it's such an important thing and it just is skipped without mentio…
> does anyone know, scoped style rules are here to stay or not? There is the @scope CSS directive. It is part of the CSS spec now. MDN even says it is supported by all latest browsers. > in HTML spec is not allowed in body Parts of the body can be encapsulated in the shadow DOM; and the shadow DOM allows its own tags.
Re: CSS-in-JS: The Great Betrayal of Front End Sanity
#13Re: CSS-in-JS: The Great Betrayal of Front End Sanity
#14Earlier quoted context omitted.
> does anyone know, scoped style rules are here to stay or not? There is the @scope CSS directive. It is part of the CSS spec now. MDN even says it is supported by all latest browsers. > in HTML spec is not allowed in body Parts of the body can be encapsulated in the shadow DOM; and the shadow DOM allows its own tags.
Thanks. That's a JS-only thing then right?
Re: CSS-in-JS: The Great Betrayal of Front End Sanity
#15Re: CSS-in-JS: The Great Betrayal of Front End Sanity
#16Re: CSS-in-JS: The Great Betrayal of Front End Sanity
#17I’m so tired of reading LLM slop articles. I don’t mind someone using AI assistance but it should be embarrassing to put your name next to something you so obviously didn’t write. I don’t remember who said it but I really like this summary: posting LLM slop as your own writing destroys the reader/writer contract. Normally you’d expect the writer to have spent more effort on a piece than the reader. But now the reader…
The article is certainly shallow, and its title is clickbait, and it says things that will make some web developers roll their eyes, and of course LLMs are now available to anyone — but what makes you think this particular article was written by an LLM? What are the telltale signs?