tailwindcss-jit VS Papercups

I found this GitHub issue where someone wants to use CSS variables for padding, like so: p-[var(--app-padding)]

Just cruised the JIT docs & code on GitHub (merged into main branch).

> add non-default variations (mostly different heights/widths than what it ships with).

Check out https://github.com/tailwindlabs/tailwindcss-jit. It got released 3 weeks ago, and supports variable variables in width and height now.

About two weeks ago, Adam Wathan announced a new Tailwind experiment: Just-In-Time. In this article, I'll tell you what it's all about, and how you can take advantage of it.

In the latest Storybook update, we finally got support for PostCSS 8. So, to celebrate this occasion, I've put together a React Storybook environment that includes everyone's favourite utility-first CSS framework: TailwindCSS. The environment also utilizes the TailwindCSS JIT compiler & Webpack 5 to bring the build times as close to instant as possible. And to top it off, the repo includes a simple GitHub action that deploys the Storybook to GitHub pages every time something is pushed.

Tailwind CSS 2.0 with the Just-in-time version

It’s not a setup issue. The JIT works differently: there’s no “purging”. And the issue I described is a known problem: https://github.com/tailwindlabs/tailwindcss-jit/issues/71

Sidestepping the broader conversation, this "JIT tool" is apparently a postcss plugin, which means you have to spawn postcss process (e.g. at every save events or have build tool do the same).

Enter @tailwindcss/jit, a drop-in replacement (though not with 100% feature parity yet) that collects the classes used by your files and only generates the requested classes.

The best language for the task at hand, when presented with time constraints, is the one that you already know well. OP said in the article that they authored Papercups [1]. Adopting Elixir for a websocket-push service makes a lot of sense, then. However, why don't you learn Elixir, some OTP, and then reconsider that question? You could be missing out.

[1] https://github.com/papercups-io/papercups

https://github.com/papercups-io/papercups - 5.2k stars, uses Phoenix 1.6

Papercups

Shameless plug here if anyone is interested in an open source live chat tool check out https://github.com/papercups-io/papercups

Phoneix - Elixir

We're a live message tool and it is basically what Elixir is built for https://github.com/papercups-io/papercups.

The Elixir community has been great and incredibly friendly. I originally was worried about the size of the community but that hasn't been an issue the community has been super helpful. I also think the annual stackoverflow usage surveys are very misleading because most of the community's questions get asked in ElixirForum and not on Stackoverflow.

Phoneix is the web framework of Elixir which is very similar to Rails but minus a lot of the magic has been very helpful for our productivity as well.

If I had to built another service that is websocket heavy I would definitely use Elixir. Even if it was a standard crud app I would still most likely choose Elixir.