After getting tired of Photoshop's magic wand failing on product photos, I built this color replacer with features most online tools don't have:
• HSV tolerance (not RGB) - Catches all blues regardless of lighting while ignoring whites/grays that RGB tools pick up
• Magnetic lasso-style edge snapping - Uses Sobel edge detection so polygon vertices snap to object boundaries automatically. Green vertices = snapped, yellow = free placement
• Multiple independent color pairs - Replace 5 different shades with tight tolerances instead of cranking up one slider and getting color bleed
• Preserve shading toggle - Change a pink shirt to blue while keeping all fabric folds, shadows, and highlights intact
• Editable polygons - Drag vertices after closing, undo points, hide overlay while keeping selection active
• Remove colors → transparency - Perfect for background removal when you know the bg color
Problem with RGB: White (255,255,255) is mathematically close to Light Pink (255,182,193). HSV separates Hue from Saturation/Value, so you can target "all pinks" while excluding "anything low-saturation" (whites/grays).
Free, browser-based, no account needed. Built for e-commerce product recoloring and design mockups where simple flood-fill tools fail.
While I understand your argument about IE6 which was shipped with Windows, Chrome didn't have that advantage for a long time - it's only now that Android phones and Chromebooks are shipped with it, but I don't know of a single person who does not download Chrome on their Windows Desktop too - even now when Edge is based on Chromium! Firefox has always been my primary browser (it still is, I'm typing this in Firefox), but say what you may, Chrome has taken the internet forward in many aspects. I work on an in-browser CAD tool, and I can see how vastly better Graphics performance is in Chrome when compared to Firefox for example (and it's just one example).
But then again, everyone says Google is evil to have made their own browser, but most of the world is using it - one would guess they must have done some good things with it (so taking humanity forward in some capacity etc.). Some are even criticizing Google from its own browser - I hate the fact that it made Firefox lose their market share, but I also understand it can't all be because the big corp brainwashed everyone (sure it would be a significant part though).
There's just one difference. "You are being advertised" is technically wrong. A product is being advertised to me, and yes, I have to look at it as a cost of using their service. They are advertising masses to the product companies, and product to the masses, but not 'personally me'. There's a huge difference here. I look at it more like a mutual contract between me and the 'free' service. They're not selling "me", it's more like you scratch my back, I scratch yours.
It has just reduced to the new "cool kids" thing to say "if you're not paying for the product, you're the product". You are saying it usually means "selling your data" - while most of these websites clearly state in their policies that they DON'T sell your "personally identifiable" data in any manner to third parties. So that's that. Of course, it means they could aggregate the data and sell that, but then it really doesn't void my privacy much. Is Google getting benefited from my data? Definitely. Am I getting benefited from Google's services? Definitely. Does Google know much about me? Yes. Is Google selling my personal data? No. One just needs to be aware of what they are sharing with these service.
I'm judging only from its debugging capabilities - and it looks like even now there's no (open to all) way to do that. Compared to that, C even if that's 20 years old code too, has some great debugging tools for it.
I newly joined this company, and they have 20 years old codebase which is mix of C and Scheme code. The only way they debug the massive Scheme part is using print statements. And I only have bad things to say about that. :( If there's a better way all of them have been missing, I'd love to hear that. I've learned that they have adapted the MIT Scheme implementation to add Object Oriented features, and it "kind of" works like an object oriented language, except when it doesn't - which happens a lot. It's a mess.
Yes, every commenting system which has an 'upvotes' system should learn from reddit's sorting, because it's the only major one I've seen so far which takes care of this 'problem' of early comments get more votes, later ones get buried.
• HSV tolerance (not RGB) - Catches all blues regardless of lighting while ignoring whites/grays that RGB tools pick up
• Magnetic lasso-style edge snapping - Uses Sobel edge detection so polygon vertices snap to object boundaries automatically. Green vertices = snapped, yellow = free placement
• Multiple independent color pairs - Replace 5 different shades with tight tolerances instead of cranking up one slider and getting color bleed
• Preserve shading toggle - Change a pink shirt to blue while keeping all fabric folds, shadows, and highlights intact
• Editable polygons - Drag vertices after closing, undo points, hide overlay while keeping selection active
• Remove colors → transparency - Perfect for background removal when you know the bg color
Problem with RGB: White (255,255,255) is mathematically close to Light Pink (255,182,193). HSV separates Hue from Saturation/Value, so you can target "all pinks" while excluding "anything low-saturation" (whites/grays).
Free, browser-based, no account needed. Built for e-commerce product recoloring and design mockups where simple flood-fill tools fail.