It's silly to discard GTK as overcomplicated because it is designed for more than "a few buttons and some text". Surely the author's JSON idea would end up in t

It's silly to discard GTK as overcomplicated because it is designed for more than "a few buttons and some text". Surely the author's JSON idea would end up in the same place. After all, it's a GUI toolkit that is going to be serving the needs of many different applications; just in the flavour of the month, instead of a shared library. (And as far as GUI toolkits are concerned, GTK generally strikes me as quite modest. It has a lot of widgets, but they aren't terribly redundant, and it doesn't have stuff like an analog clock widget for that one developer who wanted an analog clock. And the odd ones that are there, like the different kinds of buttons, are pretty transparent quality-of-life helpers where it's clear how to make your own if you want). With that said, nobody cares about GObject Introspection in OCaml. So unless you want to maintain that, you're stuck with an ancient wrapper library for GTK2, which is pretty sad. I definitely would avoid it. If we're going to discard GTK for a reason that isn't "I probably picked the wrong language", I'd add that it's challenging to target non-"Linux" platforms with it, but then your best option for that is Qt, and if you pick Qt you probably aren't using OCaml… So I can see where he's coming from, at least for OCaml, but, uh, JSON?