piyush_soni

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.

I liked the clean interface and on-point functionality, but I loved the loading performance! Several websites which I regularly use for doing JSON diff are extremely slow for large documents. This one does it instantly. Nice work!

Man. They way they market and sell 'average' stuff which won't even raise an eyebrow if it came from any other company is remarkable.

I don't know where you see such a line in Onshape's ToS. Can you point me to it? IANAL (and speak only in an individual's capacity who is hopefully reading the same ToS), but the public documents you create as a free user are essentially in "public domain", so even though you still 'own' it, you grant a broad, "worldwide, royalty-free and non-exclusive license to any End User or third party" to use the intellectual property within that document "without restriction". This includes the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of it.

I'm sorry, as far as I know the leadership is pretty clear on that. For a foreseeable future CAM will remain a Pro only feature.

> But I just know, at some point Onshape will start charging us freeriders.

- I don't know about that, may be, may be not, but I don't know of any such plan in the short term at least. It gives University students a free 'professional' license so there's that too.

> Just fill pattern and text are always a struggle.

Feel free to create a support ticket about your pain points. Everyone can easily do that, and Onshape is surprisingly more responsive to support tickets than many other companies.

Onshape employee here. I agree with another poster that for most "non-professional" requirements Onshape's free tier is all one should need - sure, the documents remain public if you don't pay. It's prohibitively expensive to maintain the technology stack with the complexity, scale and performance that Onshape does, and its costs a lot of money. :)

Sundar Pichai. That's what changed. He's one of the most uninspiring tech leaders of today who just wants to run an already established business with more and more ads with some AI sprinkled upon everything. And cost cutting. That's all, that's his entire vision.

Then why are you using it? I tried using Gemini once on my Pixel 6. Couldn't play music on Youtube music on verbal instructions, I switched back to Google Assistant. Will try it again after 6 months now. :)

I do understand 3 * O(n) is just O(n), thanks. I was just clarifying my initial typo. However, it's still three/four times the iterations needed - and that matters in performance critical code. One is terminology, and the other is practical difference in code execution time that matters more, and thus needs to be understood better. You might not 'care about constant factors' but they do actually affect performance :).

Yes, wrote quickly without thinking. Even if it doesn't change the complexity, it's still three or four times the operations.

Oh yes, sorry I meant to write 3 * O(n) which though doesn't change the order is still three times the operations. The example I was remembering was doing filters 'inside' maps.

> Keep data transforms and algorithmic calculations in functional style

What annoys me greatly though is kids coding various 'fancy' functional paradigms for data transformation without realizing their performance implications, still thinking they've actually done the 'smarter' thing by transforming it multiple times and changing a simple loop to three or four loops. Example : Array.map.filter.map.reduce. Also when talked about it, they have learned to respond with another fancy term : "that would be premature optimization". :|