> why "ugly HTML" is rarely am issue. at least not in my experience
Fascinating, 5/5 Tailwind projects I have ever used, from YC companies to multibillion dollar private companies have had "ugly HTML". Not every single HTML element is a component, and top levels of components still need to by styled using tailwind's long lists of classes.
since you mention Picard and wanting contribute to MusicBrainz. I'm working on a new fast tagger[1] in the spirit of Picard or beets. Just a little different and more scriptable
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
What are you using for tag reading/writing in Go? Robust, complete options are non-existent in JavaScript land (Deno, Bun, Node, etc.), so I ended up creating a Wasm version of TagLib with a TypeScript API.
Cooool, I love that you arrived at the same conclusion! Mine's not ready for its ShowHN, but as an enthusiast, I'm super-excited to dig into yours. Very nice work!
Hi all,
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.
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.
This was my thinking as well. Also if they have metrics that show the top suggestion is picked 90% of the time after x characters (or even user based metrics like Bob always picks the top suggestion after 10 characters), then they can preemptively generate the response to the top suggestion leading to near instant feeling responses.
Nah, I don't buy it. Chinese as plenty of programmers who can read code as well as you. This dude is literally dumping symbols. There's no proof that it's actually a backdoor.
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