hyperloglog VS Tailwind CSS

To keep tabs on what’s happening, we use Axiom for logs and Grafana for dashboards and alerts. We pipe all of our logs from most services straight into Axiom and have some pre-defined filters there that help us understand whats going on. With Grafana we have a bunch of custom dashboards that help us triage issues, and more importantly, alert us if some metrics are looking off. Without Grafana, Sliplane could not exist!

I've heard good things about Axiom[0], especially for high scale needs.

0: https://axiom.co/

If your app is instrumented with OpenTelemetry, I'd really recommend something like SigNoz (https://signoz.io/) or Axum (https://axiom.co/) (or even Baselime.io but their application is a mess to work with)

1. Axiom has a generous free plan (not sure if it's self-hostable)

Great choice of monitoring and analytics tools (Sentry, Axiom, Posthog and Uptime Kuma) coupled with amazing Slack integrations that allowed us to iron out any issues way before the traffic spike while the troubling features were still fresh from the oven.

For the last 1.5 years, I have been using Axiom for all of my logs ingestion, querying, and monitoring needs. It is a great product and I never had one issue with it in my time using it. Spoiler alert, even today, when it failed it was actually my fault, but let's see what happened.

Axiom

Axiom is an observability backend with OpenTelemetry support. I chose it for my recent project because of its cost, especially for hobby projects or serious projects in its early phase. They provide a JavaScript library that you can use as transport for pino.

Axiom has a great integration with Next.js: https://axiom.co

Styling: Tailwind CSS

I primarily work on Windows, though I also use Linux, so I needed a cross-platform solution. I chose Electron for its flexibility and paired it with Svelte, TailwindCSS, and Vite-Electron. Vite made dev setup fast and clean, which I really appreciated.

TailwindCSS

> When I’m trying to debug a web app, it’s hard to orient myself in the DevTools if the entire UI is “div soup”

That’s tame. Try adding some Tailwind CSS.

After monitoring Tailwind CSS since its early days, and believing I had some pretty serious philosophical disagreements with it, I recently took an opportunity to try it out in earnest, and it is so mindbogglingly obnoxious in dev tools that I think surely I must be missing something. How do people cope with this stuff!?

If you’re not sure what I’m on about, go through some of the sites linked near the bottom of https://tailwindcss.com/. In the Inspector/Elements panel, the DOM tree is a bloated mess with a class attribute which amounts to inline styles or worse, commonly hundreds of characters long, discouraging you from using semantically-meaningful classes, and duplicating stuff enormously rather than using sane selectors; the mostly-better ones are those that have data-sentry-{element,component,source-file} attributes. The styles subpanel becomes utterly unnavigable.

(I’m not saying everything in Tailwind is bad; I think I am likely to use a limited utility styles approach more than I did in the past, and there are a couple of other things that are provoking thought in me, and I think it would be more suitable in apps than in marketing-style websites. But the total embodiment of it is not for me.)

We use dynamic importing to solve a strange bug in Tailwind CSS that is marked as solved but still occurs.

UI: Preact + Tailwind/shadcn

Styling: Tailwind CSS (Assumed, common with Next.js)