True... this was a conscious trade-off at Figma since it needs to support designs for web, iOS, Android, etc. That unfortunately means it doesn't map 1:1 to any of them.
I'm guessing the comment was downvoted because the suggestions are mentioned in the first paragraph of the article...
> After trying a few stopgap solutions—like purchasing M1 Maxs for our team—build times gradually reverted to their original pace; Ccache and remote caching weren’t enough either.
Strongly recommend either The Way of Kings or Mistborn. They're the first books in two separate series of his. The Way of Kings is epic fantasy. Mistborn is somewhere between fantasy and YA.
Neat! In my experience jump flooding on the GPU is faster than any CPU side approach for images bigger than a few hundred pixels. It's O(n ^ 2 log n) which sounds really expensive, but it requires just O(log n) draw calls.
The link you provided also describes a GPU amenable approach, but it says that jump flooding on the GPU is faster.
> For a more efficient GPU-amenable method, see also jump flooding by Rong and Tan. Their method generates a closest point coordinate field from which a distance field can be derived.
Ah, thanks for clarifying! I think someone already called this out above, but the benefit of the approach I describe is that you only need one sample per pixel. Four samples per pixel starts to feel pretty slow on my machine, and I suspect you'd need more than that to make the averaging approach look good.
There are definitely more physically accurate ways to render soft shadows, but AFAIK they all involve some kind of bounce lighting where light bounces off of objects in the scene and indirectly lights other parts of it.
This looks great when combined with area light sources, like you suggest, but in my experience it's too slow for interactive demos.
I just pushed something that will print more info when that error happens. If you or anyone else runs into it again, please post the error here so I can fix it :)
The page's domain and title are disappointing to me.
Using sexualized language can create an environment that is unduly hostile to women, even if this is not intended. Many of the biases against women that such language provokes are totally unconscious, so even if the intent is not harmful, it can be bad regardless.
Just to play devil's advocate: what if you define progress as "that stuff" that will increase the general well-being of the greatest number of people over the next 20 years? With that definition, does technology-powered automation still count as progress?
Out of curiosity, what platform do you design for? I often make designs for web and mobile web, and I want my text to look the same in my design tool as it does on the platform I'm designing for. Since mobile devices don't support sub-pixel antialiasing, I don't want it enabled in my design tool either.