Comment 8 for bug 1390890

Answers to #4:

3) It is not that simple. The concept of how the textures are represented can be abstracted away, but it is much simpler if we only have on engine to care for in either case. For example, there is one class that is loading an image from disk and creates a texture out of this. This would need changes for texture atlases to support images that never change and are rendered always together and dynamic textures like the rendered richtext. That is something that the software renderer would not care about.

5) We have no data in either case. Could be that fallback software is used by many people, could be that it was not used in years. We can only remove the support and wait for the outcry. Or are there other options?

The 0AD discussion actually is supporting my case very strongly. They are even much more aggressive about it actually.

So for me the remaining issue is how to draw minimaps on the server. We can always fall back to tinos suggested solution for that.