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
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.
+1 for restfox. moved from insomnia a few weeks ago. the UI could do with some polish but it's great other than that. plus it even has tabs, and can run in only a browser
> if you wish to change your design, you'll have to update multiple templates instead of one CSS rule.
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
and you can also click on a request in the network tab and find out the line of code triggered it, including callstack
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
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