open-props VS star-history

There's still some boilerplate, but I'm a big fan of Open Props[0] because it takes a hybrid approach. CSS isn't necessarily reinventing the wheel, but allowing for easier / more powerful approaches to difficult layouts or things that would otherwise require JS. Bootstrap is fine but troubleshooting advanced layout issues involves a lot of inspecting elements to see what styles are actually being applied (at least in my experience, YMMV) so I'd personally always bet on CSS.

[0] https://open-props.style/

I don't quite get the hate for having CSS in another file. Do you also put all your react stuff in one single file ? That same logic and argument can be applied against all modularization.

And really 20-50 tailwind classes in a single element is VERY hard to read and keep in mind. No - it does not make things clear or understandable. One tends to need to re-read and scan over from the beginning and eyes glaze over. Esp if some elements only vary with a few classes missing. I guess it works for people with very high attention to detail and high amount of working memory. I only find it personally frustrating.

Maybe tailwind css works for some bright people. I did try it for a couple of projects and only felt pain.

However, the "atomic css" philosophy behind tailwind is great. I find framewroks like https://open-props.style/ far better to use.

Open Props adds to the set by providing extra custom properties for things like easing functions or animations.

> If you wanted to actually solve theming, what you should work for is not a constrained helper function like light-dark(), but instead a shared token schema. Today nearly every company has their own token schema and different ways of naming things in the semantic token layer. If we had a shard language here, not only would it be trivial to add light/dark theming (just redefine a few variables that are already provided for you), code could be shared between sites and inherit the theming/branding.

Isn't that the idea behind https://open-props.style/ (and https://theme-ui.com/ in JS land)?

I think it's a great idea, but hampered by the lack of adoption incentives for the very people that need to adopt it for it to become successful (design system/component library authors). It introduces constraints, but the promised interoperability is not really beneficial to the people who need to work within those constraints.

I do think that the real value of Tailwind comes from the utility classes, rather than css-in-html paradigm. You could achieve the same, for example, with Pollen.css [0] or Open Props [1].

[0] https://github.com/heybokeh/pollen

[1] https://github.com/argyleink/open-props

If you choose to style with plain CSS you can add design tokens as CSS variables with Open Props: https://open-props.style.

Some time ago I discovered Open Props which provides a lot of design tokens as CSS variables and started using it in some of my projects.

CSS: Open Props (https://open-props.style/)

https://open-props.style/ gives you design tokens as CSS variables. It’s CSS only and not Svelte specific.

I have some questions about the Github Star history, it's very unusual to see a ~1 year old with 20k+ stars.

It went from 6k to 15k+ stars in a few days around 2023 Christmas when global internet traffic is usually lowest, and I couldn't find any major social media posts or announcements around that time. If you're gonna buy stars don't buy 10k+ stars on one day, spread it out a bit!

https://star-history.com/#Stirling-Tools/Stirling-PDF&Date

https://www.google.com/search?q=%22stirling%22+%22PDF%22&sca...

That’s a great project you pulled off. From the time I starred it (10-12h ago I think), and upon re-checking this post, you gained 500+ stars lol.

Visualized in a chart with star-history: https://star-history.com/#nilsherzig/LLocalSearch

You can actively see a fresh "hype curve" in the transformer-debugger repo that was posted a couple days ago (https://github.com/openai/transformer-debugger) (star history https://star-history.com/#openai/transformer-debugger&Date).

Regardless of the repo's stars or how valuable it really is, at the time I saw it posted to HN, it had 1.6k stars/16 hours. What channel are people listening to to star it so quickly. I'm not implying any nefariousness, mind you, I'm only wondering where all the stargazers were referred from so fast and in such volume.

I’ve been releasing open-source projects for years now, and I’ve always wanted to see how fast my Github repo is growing compared to other successful repositories on https://star-history.com/. The problem is that on Star History, I’m unable to zoom into the graph, so a new repo that has 1,000 stars cannot be compared with a big repo that has 50,000 because you can’t see how the bigger repo does in its beginning. So, I asked GPT Pilot to build this functionality. It scrapes Github repos for stargazers, saves them into the database, plots them on a graph, and enables the graph to be zoomed in and out.

i'm a one man shop in montana, competing w/ Google, Vercel & Facebook for dev mindshare

if i did what everyone else does you never would have heard of htmx

https://star-history.com/#bigskysoftware/htmx&Date

also: https://star-history.com/#bigskysoftware/htmx&facebook/react...

Similar to http://star-history.com for GitHub repos, http://like-history.ai is a tool to help generate the like history of projects on HuggingFace.co

More details: https://twitter.com/Tim_Qian/status/1730245069259575485

yeah, he was the one that really started the madness:

https://star-history.com/#bigskysoftware/htmx&bigskysoftware...

his video posted on july 7th

Github star history graph of the batch:

https://star-history.com/#trpc/trpc&termux/termux-app&respon...