[bitwize]

Of course I know the difference. Pango is part of the "new world" in which all text rendering is done client-side. BDF is the old X11 bitmap format, used for X11's server-side text rendering. It makes sense for Pango to move away from supporting it, as hardly anyone uses BDF anymore except for backward compatibility with legacy X applications, and the world is moving away from X.

Matter of fact, rendering everything is moving to client side, hence why X is increasingly unnecessary, and why Wayland is designed the way it is.

Oh, and among "Wayland fans" you can count just about everyone who knows anything about the Linux graphics stack, except maybe for Keith Packard. So yes, getting traction is important, because no one wants to keep maintaining the broken X architecture. Xorg is largely maintained by Red Hat who have put it in "hard maintenance" mode with virtually no new development.

[dilandau]

Ah yes, the "new world" that the developers like and that ultimately complicates things for end-users, and obsoletes 30+ years of software in the process.

I prefer stability.

[bitwize]

You want to talk complicating things for end users? Does "XF86Config" mean anything to you? X only got halfway decent when the KMS driver came out, migrating much of the video hardware functionality OUT of X and into the kernel. The X server is thus now largely a state tracker for an obsolete protocol.

Meanwhile, Wayland has pretty much the same graphics server architecture that Windows and macOS had decades ago. It finally brings the Linux desktop architecture in line with the state of the art. There may be a rough transition period, but the faster the Linux community pulls together and rips the X band-aid off, the shorter that period will be.