I'm afraid you vastly underestimate what it takes to produce a competent GUI toolkit. Performance, portability, layout control, theming, keyboard control support, accessibility for things like screen readers, and, of course, a sane API.

And I don't mean the code, I mean the design / architecture / UX expertise.

▲

asdfsa32 a day ago | parent | next [-]

In what sense am I underestimating it?

> Yes, it will be a grind to get anything working without those

Those being the GUI toolkits like Qt and KDE one.

But yes, I agree, I have done UIs in low level (Skia) and high level (web, android) and I know it is a lottttt of work.

	▲	nine_k 19 hours ago \| parent [-]
		> In what sense am I underestimating it? Given the design complexity you're aware of, the need for practical testing to iron out the kinks, and the burden of converting anything important to a new GUI toolkit, I find the chances of this happening rather slim. On one hand, AI tools can help develop the toolkit faster and easier. On the other hand, the same tools just make the task of dealing with GTK and Qt easy enough for many not to bother, while enjoying the network effects of relying on a large and established project.

▲

a day ago | parent | prev [-]

[deleted]