What gives me real climate anxiety:
Not that we're doomed to fail, but that the options for success are far more accessible, just and beneficial than we realise
And that we'll let it slip past anyway because it's easy for incumbents to spread lies and protecting profits.
🚨 IT’S TIME FOR ROUND THREE 🗳️
32 terrible tech industry figures have now been narrowed down the top 8 in a competition for the honor of being 2022’s Worst Person in Tech.
Make your voice heard, and get your chosen ghoul to the finish line!
@diacritica@penpotapp No question, you’ve garnered huge awareness, well earned. 👍 Still early days, so interested to see how the momentum builds and where the community evolves.
Heart on sleeve time (!) stories like this, well they _really_ do just make it worthwhile.
Heartening to know something you've had some small role in can be out in the world, helping _anyone_ when they most need it.
Proud to be part of the…https://t.co/htJjrqDk6F
📣 The 2022 Design Tools Survey results are live!
🧠 We’ve spent the last month crunching the numbers from 4,260 responses, and we’re excited to share the findings!
🧵 Here are some interesting highlights (link to full results at the end)...
@chrismurphys Disgusted by @nswpolice treatment of #dannylim — he’s a stirrer, but mostly wants to make people smile. Last time was in Barangaroo. @NSWLabor@GreensNSW gonna stand up for an old guy’s democratic rights?
@skuwamoto@figma …oh yeah, and another ‘papercut’— not being able to use a locked object as anchor to align another, i.e. select locked item, Shift-click another and use align buttons to position the unlocked object relative to the first.
@skuwamoto@figma Better handling of nested components, like over-ride retention when swapping Components — elements must be same name AND same layer hierarchy. That breaks if you want to save a set of Component overrides as a new Master Component for reuse.
@skuwamoto@figma Something like the @AdobeXD Repeat Grid that works *inside* a Component — Lists are fundamental to UI and workarounds like slots can massively blow out component variant needs.
@helloiamrob@skuwamoto@figma Yes! I’ve long wanted granular view history, ie. Back/Forward through where I’ve been working in and across files, a la the great @Sketch_Runner — Kinda/sorta have it via selection being part of the Undo stack, but that breaks down quickly.