They can't, a library implements a specific API.
>except they still boil down to the exact same interface. "Button X was pressed... button Y was released... moved +X+Y"
Well no, with multitouch the interface has changed from that to a series of events, and you have to handle gestures too. Some apps still don't support these. This isn't just for mobile devices, laptops all have these touchpads now too.
>Or are you going to tell me that we should support a screen whose resolution is measured in _more than_ billions of pixels wide and tall?
This would be for pointing devices, so yeah, with a high DPI mouse then you might want to make it 32-bit or 64-bit. This wouldn't be for billions of pixels but to subdivide into many fractions of a pixel. Example: the original Win32 API only uses 16 bits for mouse coordinates, so a new API is needed and the apps need to be changed if they want to take full advantage of that mouse.
>That doesn't change the fact that unicode is broken in most apps.
Please report those bugs to the developer, that should be fixed.
>Programs that do handle that type are exactly what I want to stop. I absolutely never ever want to copy HTML from somewhere but there's often no way to disable it. Formatted text? Trash. Send me a file. Picture? Trash. Send me a file.
I can't agree with this, I copy formatted text and pictures all the time. Your program should have the ability to remove the formatting.