Eldar
@eldar.social
Mostly tech shit posts 💻️ / space nerd posts 🚀
🇨🇦 Montreal, QC
🇨🇦 Montreal, QC
They always get sooooo close to "why did we invade a peaceful neighbour", but never quite get there...
January 11, 2026 at 9:26 PM
They always get sooooo close to "why did we invade a peaceful neighbour", but never quite get there...
Reposted by Eldar
In my case, Russian (grew up with), German (years of study in high school), and now French (living in Quebec) are all wildly inconsistent 😅
January 10, 2026 at 4:40 PM
In my case, Russian (grew up with), German (years of study in high school), and now French (living in Quebec) are all wildly inconsistent 😅
Same words being gendered differently in different languages is infuriating. Like someone bumped up the difficulty to hard for no reason.
January 10, 2026 at 3:59 PM
Same words being gendered differently in different languages is infuriating. Like someone bumped up the difficulty to hard for no reason.
CSS purists will probably get mad, but I really do thing TW is less of a framework, and more of an atomic CSS spec at this point.
January 9, 2026 at 8:08 PM
CSS purists will probably get mad, but I really do thing TW is less of a framework, and more of an atomic CSS spec at this point.
This extends to tools like Webflow, which can train AI models to generate TW classes, a simple and relatively precise output target. Same with Figma UI generators. It's easier for these tools to get good LLM outputs when the "compile target" is well-defined. For better or worse, TW is that target.
January 9, 2026 at 8:08 PM
This extends to tools like Webflow, which can train AI models to generate TW classes, a simple and relatively precise output target. Same with Figma UI generators. It's easier for these tools to get good LLM outputs when the "compile target" is well-defined. For better or worse, TW is that target.
So, by opting into atomic classes, you make LLMs' job easier. By opting into TW atomic classes specifically, you also give them a common convention to work with. LLMs are dumb, cannot reason, no matter how much folks insist on the opposite. More conventions + greater volume of code = better outputs.
January 9, 2026 at 8:08 PM
So, by opting into atomic classes, you make LLMs' job easier. By opting into TW atomic classes specifically, you also give them a common convention to work with. LLMs are dumb, cannot reason, no matter how much folks insist on the opposite. More conventions + greater volume of code = better outputs.
2. Classes live directly inside of UI code, as opposed to separate files, so the task of generating output is simpler: no need to apply changes in multiple places
3. Composing classes, whether TW or not, is also standardized because... well, that's just how HTML classes work
3. Composing classes, whether TW or not, is also standardized because... well, that's just how HTML classes work
January 9, 2026 at 8:08 PM
2. Classes live directly inside of UI code, as opposed to separate files, so the task of generating output is simpler: no need to apply changes in multiple places
3. Composing classes, whether TW or not, is also standardized because... well, that's just how HTML classes work
3. Composing classes, whether TW or not, is also standardized because... well, that's just how HTML classes work
Yup, exactly. Tailwind has passed the adoption threshold where it is a de facto standard for atomic CSS. LLMs love this for three reasons:
1. The standard classnames take the vast API surface of CSS and boil it down to a common subset. Less options = more predictable LLM outputs
1. The standard classnames take the vast API surface of CSS and boil it down to a common subset. Less options = more predictable LLM outputs
January 9, 2026 at 8:08 PM
Yup, exactly. Tailwind has passed the adoption threshold where it is a de facto standard for atomic CSS. LLMs love this for three reasons:
1. The standard classnames take the vast API surface of CSS and boil it down to a common subset. Less options = more predictable LLM outputs
1. The standard classnames take the vast API surface of CSS and boil it down to a common subset. Less options = more predictable LLM outputs
Same goes in the other direction: some teams don't want to use TW for layouts for... reasons..., but the TW default color scheme is **amazing** as a starting point. You could rip it out as tokens and go from there, but imagine if it was a single stylesheet you could import and go 🏎️...
January 9, 2026 at 7:06 PM
Same goes in the other direction: some teams don't want to use TW for layouts for... reasons..., but the TW default color scheme is **amazing** as a starting point. You could rip it out as tokens and go from there, but imagine if it was a single stylesheet you could import and go 🏎️...
Atomic classes nail composability. All the other solutions (styled component extensions, style-via-props a la Material/Chakra, or manual, vanilla CSS) have awful ergonomics. But full TW has high adoption costs: IDE plugin, class sorting, build step/Vite plugin).
I'd *love* a @tw/layout standalone.
I'd *love* a @tw/layout standalone.
January 9, 2026 at 7:02 PM
Atomic classes nail composability. All the other solutions (styled component extensions, style-via-props a la Material/Chakra, or manual, vanilla CSS) have awful ergonomics. But full TW has high adoption costs: IDE plugin, class sorting, build step/Vite plugin).
I'd *love* a @tw/layout standalone.
I'd *love* a @tw/layout standalone.
I keep finding myself in codebases that aren't built on TW and wanting to reach for e.g. "flex flex-col gap-2", only to realize I either have to give my <div> a custom classname and style it that way, or worse, add React props if its an existing component.
January 9, 2026 at 7:02 PM
I keep finding myself in codebases that aren't built on TW and wanting to reach for e.g. "flex flex-col gap-2", only to realize I either have to give my <div> a custom classname and style it that way, or worse, add React props if its an existing component.
Think of all of the <VStack>/<Grid> components that a bunch of design systems that don't use TW build that could be replaced with a layout util class subset of TW.
Or any design system that stuffs custom color/typo/visual token classes in a tokens.css file, but has to implement custom layout utils.
Or any design system that stuffs custom color/typo/visual token classes in a tokens.css file, but has to implement custom layout utils.
January 9, 2026 at 7:02 PM
Think of all of the <VStack>/<Grid> components that a bunch of design systems that don't use TW build that could be replaced with a layout util class subset of TW.
Or any design system that stuffs custom color/typo/visual token classes in a tokens.css file, but has to implement custom layout utils.
Or any design system that stuffs custom color/typo/visual token classes in a tokens.css file, but has to implement custom layout utils.
Kinda wish Tailwind shipped in parts:
- colors and typography
- visuals (heights, widths, borders, strokes, shadows)
- layout utils (flex/grid, spacing, gaps, positioning)
Many design systems could provide the first two, but let devs use just the latter for assembling layouts.
- colors and typography
- visuals (heights, widths, borders, strokes, shadows)
- layout utils (flex/grid, spacing, gaps, positioning)
Many design systems could provide the first two, but let devs use just the latter for assembling layouts.
January 9, 2026 at 7:02 PM
Kinda wish Tailwind shipped in parts:
- colors and typography
- visuals (heights, widths, borders, strokes, shadows)
- layout utils (flex/grid, spacing, gaps, positioning)
Many design systems could provide the first two, but let devs use just the latter for assembling layouts.
- colors and typography
- visuals (heights, widths, borders, strokes, shadows)
- layout utils (flex/grid, spacing, gaps, positioning)
Many design systems could provide the first two, but let devs use just the latter for assembling layouts.
Yea, maybe I was being too dramatic 😅 I think we'll see less code open-sourced in the future because many OSS devs are driven by the desire to share their work with humans, less so to train LLMs, and there isn't a license to "share code with humans only" right now.
January 9, 2026 at 4:04 PM
Yea, maybe I was being too dramatic 😅 I think we'll see less code open-sourced in the future because many OSS devs are driven by the desire to share their work with humans, less so to train LLMs, and there isn't a license to "share code with humans only" right now.
Reposted by Eldar
We really need a high-profile lawsuit that strikes down LLM use of open source code and docs for training. Until there is legal precedent, OSS is exposed and effectively dead as a software paradigm.
January 9, 2026 at 1:12 AM
We really need a high-profile lawsuit that strikes down LLM use of open source code and docs for training. Until there is legal precedent, OSS is exposed and effectively dead as a software paradigm.
We really need a high-profile lawsuit that strikes down LLM use of open source code and docs for training. Until there is legal precedent, OSS is exposed and effectively dead as a software paradigm.
January 9, 2026 at 1:12 AM
We really need a high-profile lawsuit that strikes down LLM use of open source code and docs for training. Until there is legal precedent, OSS is exposed and effectively dead as a software paradigm.
ITerm2 is still the least buggy of the bunch
January 8, 2026 at 7:44 PM
ITerm2 is still the least buggy of the bunch
Just needs an icon theming feature that replaces all icons with cats now ;)
January 8, 2026 at 6:10 PM
Just needs an icon theming feature that replaces all icons with cats now ;)
Did YouTube break their Queue feature again? 🤔 It disappears when navigating away from videos to Home or Subscriptions...
January 8, 2026 at 6:08 PM
Did YouTube break their Queue feature again? 🤔 It disappears when navigating away from videos to Home or Subscriptions...
Damn, I didn't realize how bad the RAM prices have gotten. I sold of a bunch from my homelab in September, and the same sticks now go for 3x 😬
January 8, 2026 at 3:43 AM
Damn, I didn't realize how bad the RAM prices have gotten. I sold of a bunch from my homelab in September, and the same sticks now go for 3x 😬
😔
January 7, 2026 at 9:56 PM
😔
It's not. He spent his first few days pushing back on moving the Smithsonian Space Shuttle to Texas.
January 7, 2026 at 4:46 PM
It's not. He spent his first few days pushing back on moving the Smithsonian Space Shuttle to Texas.
Been working a 3 days a week contract for the last few months. 4 day weekends every week is very nice. Highly recommend 👍
January 7, 2026 at 3:41 PM
Been working a 3 days a week contract for the last few months. 4 day weekends every week is very nice. Highly recommend 👍