from Hacker News

Tachyons – A CSS Toolkit

by impoppy on 7/19/23, 12:49 PM with 82 comments

by omegabravo on 7/19/23, 1:22 PM
Tailwind before tailwind.
It's strange, I never saw the point of it, however I saw the value in tailwind almost straight away.
I think that might be the difference in examples. The tachyon examples always look uninspiring.
by meerita on 7/19/23, 2:39 PM
The project is outdated. The grid system is not using any CSS3 feature. So, yeah, it's an old framework. If you want better features, you may go Tailwind CSS.
by mska on 7/19/23, 3:20 PM
This is really Tailwind before Tailwind. I didn't know about it.
I'm working on a css style copying project on the side (DivMagic https://divmagic.com/) and I might add Tachyons as an option there
by stcg on 7/19/23, 3:35 PM
> Functional css for humans (https://github.com/tachyons-css/tachyons)
What makes this 'functional'? Is it related to functional programming? Or is it used as a synonym for 'usable'?
by toastal on 7/19/23, 1:59 PM
Quick fix:
```
  - .sans-serif {
  -   font-family: -apple-system, BlinkMacSystemFont,
  -                'avenir next', avenir,
  -                helvetica, 'helvetica neue',
  -                ubuntu,
  -                roboto, noto,
  -                'segoe ui', arial,
  -                sans-serif;
  - }
  + .sans-serif { font-family: sans-serif; }
```
I already set my preferred sans serif in my user agent; if you don’t care enough about the design to provide a real font stack, I don’t need your site trying to override my preferred default with Ubuntu, Roboto, or ugh Arial. If you just want something sans serif, please just fall back to the user agent so users can define the value.
by hit8run on 7/19/23, 7:37 PM
The version 5 branch is fully ongoing. I talked to Adam and it’s already in beta. You can check out the branch on GitHub.
A few minor things still to iron out but it’s the way to go. I also maintain a version with darkmode support based on v1 :)
Feature wise it has grid, css variables and a full color palette.
by quadral on 7/19/23, 2:38 PM
I won't be using this.
The grid system is still using floats instead of flex/grid.
by umtksa on 7/19/23, 1:26 PM
I love their components page and modular system. With article components any one can create a clean, responsible blog or landing pages. As a non profesional it's a perfects system for me.
by xswhiskey on 7/19/23, 1:57 PM
I’ve been using it for a couple years now, absolutely love it. I personally prefer it over Tailwind (and don’t feel like learning _another_ css framework) and, ngl, the “components” section of the page is a big reason for it.
When I started using it, if I needed a card or a list I could go to the components section and pick one, copy-paste it and then change it to my liking. When I tried the same in tailwind I was faced with a paywall and automatically lost all interest.
by no_wizard on 7/19/23, 2:42 PM
I don't know if this is maintained anymore. Last commits are from 3 years ago
by frankfrank13 on 7/19/23, 3:30 PM
always liked Tachyons, and honestly bootstrap. If HTMX catches on I could see both of these getting popular again on over Tailwind, since you won't need a build step
by qingcharles on 7/19/23, 2:13 PM
No dark mode support? :(
by PaulHoule on 7/19/23, 1:22 PM
I like it and I don’t. I mean
```
  <b>bold</b>
```
is a little simpler than
```
  <div class=“b”>bold</b>
```
Certainly designers have struggled to think systematically enough to define a set of classes that are basically semantic even though, when they do it puts their skills on wheels because they can design it and other people can knock out pages consistent with the design.
Things like this make me think CSS needs namespaces though, just the other day I found out there was more than one library in an application I am working on that declares properties of “.dropdown” which could be a problem.
More generally you really ought to be able to pull some HTML out of page A and transcode it into page B and that means copying the styles and a lack of namespaces for id(s) and class(es) gets in the way of that. In principle you could have syntactic macros for HTML or frameworks that work on the DOM more imaginatively than React does but you run headlong into the “macro hygiene” problem.