Readit Newsroryokane commented on Vanilla CSS is all you need zolkos.com/2025/12/03/van... · Posted by u/dchest
The section “Utility Classes: Yes, They Still Exist” is unfair in its comparison of Tailwind with pure CSS. It doesn’t take into account Tailwind’s recommendation in https://tailwindcss.com/docs/styling-with-utility-classes#us... that “if you need to reuse some styles across multiple files, the best strategy is to create a component” in your front-end framework or templating language. So its example of a “typical Tailwind component” is incomplete.
A better comparison would use, for example, a React component:
function Button({ children }) {
return (
<button
className="inline-flex items-center gap-2 px-4 py-2 rounded-full
border border-gray-300 bg-white text-gray-900
hover:bg-gray-50 focus:ring-2 focus:ring-blue-500"
>
{children}
</button>
);
}
// Usage:
<Button>Save</Button>
A better argument against Tailwind would be the added complexity of having a build system and a front-end framework or templating language, if your project doesn’t already have those for other reasons.
(adapted from my better-formatted comment at https://lobste.rs/c/oznzzj)
roryokane commented on GPT-5.1: A smarter, more conversational ChatGPT openai.com/index/gpt-5-1/... · Posted by u/tedsanders
roryokane commented on Switch to Jujutsu Already: A Tutorial stavros.io/posts/switch-t... · Posted by u/keybits
Yeah, no. It'll have vanished next year.
Jujutsu’s changelog (https://jj-vcs.github.io/jj/latest/changelog/) goes all the way back to 2022 and shows there was a release as recently as two weeks ago. I don’t see why the maintainers would stop at this point.
Also, from Jujutsu’s README (https://github.com/jj-vcs/jj#mandatory-google-disclaimer):
> I (Martin von Zweigbergk, martinvonz@google.com) started Jujutsu as a hobby project in late 2019, and it has evolved into my full-time project at Google, with several other Googlers (now) assisting development in various capacities.
Most of them aren't defined as rigorously as a dictionary would do, it's more like trying to come up with a plausible description for each word.
"day" might be "time in which the sun goes round the earth" even though that's not technically correct.
"sit" could be "to take a chair" and "sat" might be "to have took a chair"
"moth" is "a bug that flies and likes to eat cloth", and so on.
I made the “sit” gloss long: “to rest your body on your bum (while your bum is on a thing such as a chair or the ground) while your back is up”.
I'll defer to my fellow liberal men:
https://www.reddit.com/r/LeftWingMaleAdvocates/wiki/missions...
I don’t see anything specifically about boyhood or childhood on that page or on the rest of that sub-Reddit’s wiki. Do you have a more precise link?
roryokane commented on Protest footage blocked as online safety act comes into force freespeechunion.org/prote... · Posted by u/Bogdanp
Context: the Online Safety Act (https://en.wikipedia.org/wiki/Online_Safety_Act_2023) is a law of the United Kingdom. Previous discussion on Hacker News: https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...
roryokane commented on I should have loved biology too nehalslearnings.substack.... · Posted by u/nehal96
I am not a native speaker, but the two words do not sound even remotely the same.
How does this mistake happen so often? Can you explain people's thought process a bit? Is it just: "Something something 'seg...' ... ah I know, I will simply use another random word that starts with the same 3 letters and doesn't make sense in this phrase!"?
Also this is the first time I see it.
> the two words do not sound even remotely the same
Pronounced correctly, “segue” sounds just like “Segway” – not like “seg-oo”, as you might have assumed.
• Which of axe-core’s rules (https://github.com/dequelabs/axe-core/blob/develop/doc/rule-...) LLMs violate most often
• Which groups of users are most affected by those rule violations (e.g. blind users or deaf users)
• Whether it’s likely that I unintentionally violate those same rules in web pages I write
Examples of rule violations and statistics on most-violated rules would make the website more convincing by showing that the detected accessibility errors reflect real problems. It would rule out that the only detected error was a single noisy false positive rule in axe-core. I bet that most readers are not familiar enough with axe-core to trust that it has no false positive rules.