commotionfever
//go:fix inline and the source-level inliner
then, inside your Button, you get a small bit of markup and your class names. makes it easy to see which markup gets which styles
that's also why the other discourage use of @apply, and why "ugly HTML" is rarely am issue. at least not in my experience
---
that said, if you're using Tailwind in an environment where there's no components, fragments, partials, whatever - then this might make sense
It makes it's best attempt to match with MusicBrainz, but if there's no match it it offers links to pre-seed MusicBrainz with tools like Harmony
it also includes a web interface to manage imports from external sources.
Hope you like it
Show HN: Organizing and tagging large music collections in Go
Wrtag, a new suite of tools for automatic music tagging and organization
I've been working on a new suite of tools for music managment. I've you've used beets.io or Picard, you get the idea. They are great tools but for me were not fast enough and hard to grasp. wrtag is fast enough that the filesystem can be the source of truth, so no need for a sidecar database which can get out of sync
it also includes a web interface to manage imports from external sources.
Hope you like it
Show HN: New Go library for audio metadata read and write
https://github.com/sentriz/go-taglib
The first to support as many file formats, writing, while still being portable and CGo free (via a WASM binary and Wazero)
Show HN: Untree: like gron but generalised on indentation
Show HN: flagconf: Environment variable & config file parsing for Go stdlib flag
Hare 0.24.0 Released
Go 1.22 Rangefunc Experiment
it's great for converting nearly any format to json for querying or transforming with jq
so with 16ths, you'd typically see 1/16 & 2/16 have zero to little amplitude, 3/16 & 4/16 have most of the energy. 4 maybe even a little less so.
which can't be done by sidechaining. also phase alignment with the kick is important
the biggest usecase for me is taking some csv, toml, xml, whatever and converting that to json so I can pipe to jq
this comes up on every tailwind post and it isn't true. tailwind encourages you to not repeat yourself by making reusable components (or fragments etc) instead of reusable classes. that way if I want to see how the button both looks and works I only have one place to look
even if you don't do this, with tailwind you encode your design system (colours, spacing) etc in the config file so even copy pasting everything will get you something consistent
https://tailwindcss.com/docs/utility-first#maintainability-c...
also with react dev tools you can click somewhere on the page and see the react component, it's props, etc. similar tools are available for other frameworks