mirror of
https://github.com/love2d/love.git
synced 2026-08-16 00:02:12 +02:00
rude
3fe9b2ff16
Users (or lovers) do not get to choose which implementation of a module they would like to use. The abstraction is for dealing with portability issues, not for giving people the ability to choose an alternative (inferior) backend. The best choice for any platform/situation should at all times be the *default* for that platform/situation. If this is not the case; it's a bug (that is easily fixed). Any module should provide the functionality promised in the docs. The lover (or user) should not care how, and if [s]he does, [s]he does still not get to choose. Also, a related note: duplication of wrapper code is something I especially wanted to avoid when I first (or should I say ... "eventually") formed the current architecture. --HG-- branch : minor