The binary makes it so we don't have to include npm

If you have other npm dependencies, it's recommended to include tailwind the normal way

I think it was actually added because DHH asked for it, for rails

(or maybe that was incidental, either way I remember reading somewhere that DHH wanted it for rails)

I remember rails.

Wow… just googled it. It’s very alive and well.

yeah, they just made a rails foundation too

To think of all I’ve been through… and I could have just started and stayed with rails.

lol yes

So… this strays into Basic Web Dev Knowledge Questions… but why is a Tailwind binary type approach better than including a script tag?

More optimization?

Side question: I was including arbitrary hiccup (not rum) copy-pasta HTML with tailwind classes and it wasn’t, I think I recall, rendering correctly until I blindly included Tailwind via a script tag… is that expected?

Tonight is about Understanding Tailwind In Biff, it turns out.

I’ve been using Hiccup at times as opposed to Rum (confession).

Oh, I see what you were asking earlier. (this is I think what you're referring to: https://tailwindcss.com/docs/installation/play-cdn) Optimization is a big part. There are tons of tailwind classes, so if you use the CDN file, it'll include a bunch of stuff you don't need, making your app slower to load for users. Also, there are certain special classes you can't use, e.g. w-[14px]. (https://v2.tailwindcss.com/docs/just-in-time-mode)

Ah, gotcha. Yeah. That’s what I did… the CDN… then maybe downloaded it and included it by path. Because I didn’t understand what was going on and somehow not everything was getting compiled by the binary, I’m guessing.

> Side question: I was including arbitrary hiccup (not rum) copy-pasta HTML with tailwind classes and it wasn’t, I think I recall, rendering correctly until I blindly included Tailwind via a script tag… is that expected? Rum vs. hiccup shouldn't have anything to do with how tailwind is included. Maybe there was something else wrong with tailwind that was causing it to not compile your css.

I actually ran into some issues with the compiler when I started working on eelchat, maybe you were hitting the same thing

No… when I run into problems it’s because of something I’m doing. Let’s get that clear right off.

it would just keep crashing. super annoying. But I got a different binary (don't remember if I copied it from one of my other projects or if I downloaded it again) and the crashing stopped. 🤷 . I vaguely remember that the version didn't even change. maybe there was some weird corruption or something.

However, I have gotten into the habit of adding an additional arbitrary change to, say home.clj if I’m working in it and saving, to force recompilation. That seems natural as it was the way for so long with various dev situations.

If you run into problems like that again, I'd delete the bin/tailwindcss file and run bb dev again, which will cause it to re-download. If it still breaks, then I'll believe maybe it's something you're doing wrong 🙂

> However, I have gotten into the habit of adding an additional arbitrary change to, say home.clj > if I’m working in it and saving, to force recompilation. That seems > natural as it was the way for so long with various dev situations. Yep, I do that too

Ok. I’m normal then. Whew.

in fact if you just save the file without making changes that can trigger recompilation I think too

Oh, wow… ok. I thought it was hashing all the files to trigger compilation. Ok.

Overall I’ve had almost no issues (css or compilation). Biff’s been a dream compared to other situations.

excellent 🙂

thanks!

There weren't any comments, but here's the link: https://news.ycombinator.com/item?id=33721730 (It's on page 2 now)

> There weren't any comments At the time; now there are a few

That's a good answer about why not postgres. I had the same question myself. Is that in a faq somewhere? Should be.

not yet. I'll add it to the docs soon.