pabue

This tool was created out of a personal need to occasionally download specific versions of chromium. Turns out it's much more cumbersome than one would expect. It's much easier for firefox, but still not as easy as it could be. This is my attempt of simplifying the process. Maybe it's helpful for someone else too.

The code is available on Github: https://github.com/pabueco/browsers.zip

Occasionally I want to compare the performance of different snippets or NPM packages, but I'm too lazy to setup a test locally and found some of the existing benchmark sites a bit clunky, especially when trying to evaluate packages/libraries.

This is my attempt of making this easier. Let me know what you think.

The benchmark data/setup/code is stored in the URL, so you can easily share or save them. You can also share the results as a nice image.

Interesting idea and approach!

Just a thought on the design: I really feel like the gold gradients make the whole site feel 'cheap', not trustworthy and not very 'professional'. Actually makes me not want to use it. Replacing them with a simple warm yellow improves this a lot. That might be just me, but maybe it's something for you to consider.

Good luck!

Great extension, congrats on the launch!

It's really nice to use and the interface it provides (tab search, etc.) looks very good.

Not a big issue, but some of the text has some grammatical mistakes and spelling errors.

Also, is the extension itself open-source?

Very cool project, congrats on the launch!

Just some thoughts and findings:

- After creating one theme, the plus-button on the dashboard page keeps loading forever after clicking it. The error in the console seems to indicate I have to upgrade to create another theme, but some kind of message would be nice.

- I feel like the editor really needs some kind of undo functionality. It's a bit frustrating/risky to experiment with the settings after you have found a combination you like.

- It would be cool if I could change the text/language in the preview. I get this might be a bit much, so providing more examples in a dropdown of some sort could be an alternative. E.g. I would like the see how a vue or svelte component would look like. Also a terminal preview would be nice. IMO all this becomes even more important (or necessary) when you consider that people would need to pay $6 to actually see how the theme looks for their use cases.

- I feel like letting people download one theme (maybe limited to a few apps) for free would lower the hurdle to get them to pay for it. Maybe that's not a concern and people don't mind, but it would definitely convince me.

Hope there's something useful in there.

Really cool product and definitely something I would use regularly after trying basically 99% of all themes out there and even creating my own.

Best of luck to you!

There's definitely quite some room for improvement. Thanks!

Well it is very easy to miss. ;) Thank you!

Great idea. I think this will fit nicely with the info tool. Also a accessibility contrast score might also be helpful. I will take a look at that. Thanks!

This might have something to do with CSS transitions. It's not intentional. Gonna take a look at it later. Thanks!

Ohh, very cool idea. I'll experiment with that a bit and see how this could work. Thanks for the suggestion!

Oh, I totally missed adding a license... Definitely gonna add it later. In case you want to know now: it's gonna be MIT. Thank you!

Same, I'm so glad someone is taking the time to come up with all of those amazing names.

I've never build a photoshop plugin but it sure sounds interesting. I'm gonna see whats possible here. Thanks for the suggestion!

Interesting suggestion, I'll see what I can do.

Thank you! Let me know if there is anything that you're missing or that can be improved.

I initially started with this project to learn more about svelte and try sveltekit. So I never made a design or a prototype. I just had a rough idea of how I wanted it to look and then just iterated on it while building it.

Thank you!

That's a great idea! I'm gonna take a look at that.

I know what you mean but at the same time I think "toolbox for colors" describes it quite well with very few words. I also think it's best to just try the tools. But I do think that the tools themselves need descriptions and maybe even a small tutorial, so thanks for bringing that up.

Wow, thanks!

Thank you very much!

Good catch, thanks. Gonna fix that.

The color change when switching between tabs is definitely something I'm going to remove/fix soon. It didn't really bother me, but I see it now.

I also really like the color names. But I can't take credit for that, because someone else is doing all the hard work here: https://github.com/meodai/color-names Showing them in more places might be cool, but the performance might become an issue then.

Saving settings might also be a cool feature to add. I'm gonna look into that.

Thank you!

First of all thanks for the comments and info. I'm actually not doing the color interpolation myself. I'm using chroma.js[1] for the most part.

You can actually change the interpolation mode on the bottom below the color boxes. The default is LCH because I think it looks the best most of the time, but you can use LAB if you prefer that.

[1] https://gka.github.io/chroma.js/

I always saw them as separate tools because I always had predefined colors I wanted to mix/manipulate. But it's a really great idea to think more in the sense of a workflow (or steps) instead.

Thanks for the suggestion! I will see what I can do.

You're right, this part can be a bit confusing. I tried to prevent it by adding short descriptions to the modifiers but there's definitely room for improvement.

I never heard of oklab before. Guess I have some reading to do. But I also wouldn't say no to a PR that adds support for it ;)