I learned yesterday that Tailwind packages a binary so you can use it without Node or NPM, but the binary is...116MB š°
Regarding discussion under this post. What really matters in terms of size is what you send to the client. And for the production build you have compiled css only. So It's not really an issue whatever the size of binary to run tailwind locally for some specific use-case of dev env.
I'm sorry; I don't get the appeal of Tailwind at all. And this makes it even worse
More of a gravitational force than a tailwind
I guess you get the full v8 runtime along with tailwind's cli: https://tailwindcss.com/blog/standalone-cli#how-does-it-work
I don't really see any problems with this, considering the rationale: > This has made it harder to integrate into projects where using npm isn't always common, and with tools like Rails and Phoenix both moving away from npm by default, we needed to find a way for people to use Tailwind in these projects without forcing them to adopt an entirely separate ecosystem of tooling.
I kind of see a problem with needing a package of 116MB in order to apply some styles. When creating a full web-app, you should be able to fit all the needed css in a single file of about ~100kb
Well, I'm sure you've experienced "css rot". It quickly explodes in a large codebase and you'll have to rewrite the entire css from time to time to tackle this. CSS Modules helps with this. Tailwind even more š¤·
I did back in the day, but less so with more recent versions of CSS and a set of good practices. I see people flooding their markup with tailwind classes, whereas you usually just need some overarching styles.
I typically create styles that handle pretty much all types of markup and then only very few utility classes (Tailwind like classes) that you can sprinkle to emphasize something
If you want to go bananaz for a particular element, inline styles work
> I see people flooding their markup with tailwind classes, whereas you usually just need some overarching styles. Yeah, that's the flipside. I try to use as little styles/classes as possible in the "app code" and encapsulate the styling in general ui components.
I guess there's a correct and a wrong way of using Tailwind as well š
Back on topic, looking at my local install of tailwindcss it takes up 740K of disk space. So the rest of the binary is NodeJS, I guess.
> I kind of see a problem with needing a package of 116MB in order to apply some styles. When creating a full web-app, you should be able to fit all the needed css in a single file of about ~100kb Just to make sure ā the 116MB file is the build-time CLI, not the amount of CSS being shipped to clients.
part of what the tailwind CLI does is ensure that you include only their styles that you use, reducing the amount of CSS you ship š¤Ŗ
https://www.tipranks.com/news/the-fly/nu-holdings-cto-vitor-olivier-departs-eric-young-succeeds-thefly will it affect Clojure and Datomic šµāš«
i think that regardless of their feelings on clojure, they can't walk away from it now without really fucking up their org.
here's hoping they recognize that before making any grand pronouncements
narrator voice - he's going to make grand pronouncements
as someone working at a "legacy clojure, greenfield typescript" company, i don't wish it on anyone
Safe bet that any CTO's pronouncements these days will be ~80% about AI, at least for listed entities.
Datomic is well funded by Nubank with like 10 people working on it, Clojure's Nubank-funded headcount has increased also with the addition of Christoph Neumann in a devrel/growth role as well as a dedicated conference organizer
Is the news "new CTO" or is the news "a CTO lasted more than ten years!"?
Thanks @dustingetz for the plug! Iām here to work hard for Clojure and the community, and Iām happy that Nubank supports Clojure.