[schkolne]

Nice share! And glad to hear your good spirits about our debate, seems not every thread is subject to Godwin's law

I agree with you -- a complete rethinking -- I've actually spent the past couple years thinking a lot a lot a lot about this. And it seems that it's not just a matter of a better design tool, but also a way of how design works in relation to code, and perhaps how the code itself changes!

Sometimes I think that Design Systems, which feel like they came from the design side of the divide, actually was a motion that started with engineering. All the componentization of React etc under the hood really powered the process where designers make components. Before that it was more typical for designers to provide these 1-page sheets with the colors, margins, etc that were more like a style guide than a system. And perhaps the strict component-based approach is part of what's throwing us into the pit of despair from time to time.

[danielvaughn]

Same, I've been thinking about it a lot as well. Actually, since 2014. I'm kinda obsessed with the problem, because I used to be an artist so I'm really interested in the design/development divide. It would take too long to explain, but I've come to the conclusion that designers could benefit from having a textual interface. For a while I've been building a "programming language" for them: https://matry.design/