Scoping and semantics. Chunk. Extrusion Effect
Mode conflicts
You can now select incompatible modes on layers, to make it easier to diagnose layers that aren’t able to use the mode (via Jacob Miller).
Figma’s Creator Micro made me a macro pad person with its colorful, clicky keys
Figma sent a sample of its Creator Micro keypad to an Ars Technica reporter: “OK, it’s fun, I’m saying. It’s fun to have a little box for little computer tasks, rather than efficiently doing them all through one slab you must memorize under pain of being considered unoptimized. Sometimes I just twirl the volume knob up and down, with nothing playing, because it’s fun to twirl a knob.”
Are we too pedantic with semantics?
Luis wonders whether variables scoping provides enough semantic modification to justify removing explicit “background”, “border”, and “text” color variables. “What’s stopping us from maintaining a single, primitive set of variables, named as such (e.g. red-300) to match your developer’s framework, relying on scoping alone to bridge this gap?” (See the discussion in this thread on X.)
I also like this take from Nate Baldwin — primitive color palettes are inherently semantic because every lightness stop is knowingly created to be used for specific use cases. He supports this idea with examples from his work on Adobe’s Spectrum color palette.