i wouldn’t wait for “marzipan” or xkit or whatever it is.we don’t know what it is. but my guess — based on my 38 years of writing code for apple computers — is that it’s something you can use along with uikit and appkit, and not a wholesale replacement.maybe it’s a declarative api that helps make some things easier, and maybe you can make a cross-platform button more easily. maybe your table view code could be the same on ios and macos. great!but don’t expect macs to turn into large ipads all of a sudden. macs are gonna mac. apps are going to have multiple resizable windows and a menubar. targets will still be sized and designed for mice and trackpads.in other words, if you want to write a mac app, you’re still going to have to deal with the things that are inherently different about mac apps, regardless of the specific api.let’s say this thing ships in the fall of 2019, over a year from now. if past is a guide, we might imagine it would be fun to play with, but not more useful than, say, the original version of swift. (swift didn’t get really good for writing apps until swift 3.)so it might be 2020 before it’s something that accelerates mac development in any real way.you could write a few mac apps between now and then.* * *i realize that documentation on writing mac apps is hard to find these days. books on the subject are rare, and any book you find may be out of date.but…one of the reasons i made evergreen open source is so that people who wa...