Wayland

http://cgit.freedesktop.org/wayland/wayland/tree/src/wayland-client.h
http://cgit.freedesktop.org/wayland/wayland/tree/src/wayland-server.h
http://cgit.freedesktop.org/wayland/wayland/tree/src/wayland-egl.h

That's it. Those three tiny header files is all you need to be able to host or interface with a Wayland server, create and manipulate windows, get input device events, or get an EGL context for use with OpenGL or OpenGL ES (your choice). There are no configuration files (everything is autodetected and/or delegated to the kernel, enumerating display adapters, adapter outputs, input devices, etc. is done by traversing the mounted devfs file system tree).

You can use this as your starting point to implement a full blown DWM or X Windows layer, or you can use it write client applications that integrate nicely with any active Wayland server including Wayland-based DWM.

Why are you still using X Windows?

Why are you still using X Windows?
Because some of the over-engineered features from X are ones I use every day.

X's arch isn't bad because people were lazy or stupid, it's "bad" (i.e. slow) because it was required to support features your windows-fed ubanto brain can't comprehend.

X's interface does suck pretty hard though. No argument there.