You have Windows Vista, 7, 8, 8.1 and the servers. Maybe Service Packs too.
How many Linux distributions are there? How many desktop environments are there?
If you have to support Windows, there are only a few options. :-)
If you have to support Linux, there are hundreds. :-(
Regarding the animation studios, you can Google for it. Iirc, DreamWorks and Pixar both use gnome desktops.
Checkout the desktop in the title.
Anyway, it is getting away from the original comment and it feels like I have to get me a chainsaw. You know the feeling, when you are standing on a hill and the stream of zombies coming at you seems endless? That kind of feeling.
even less does it mean that it would constitute the native configuration and API/ABI for said distribution (in fact even for distribution implementing LSB, it usually is an addon environment with an additional set of libraries and an auxiliary linker to coexist with the distribution's native ones)
package formats are just containers for executable programs and metadata (dependency lists)and the two major package formats rpm and deb.
neither one accounts for platform specifics the program will have to face at runtime (from api's to the the lowliest detail, say a binary environment flag) so they dont guarantee compatibility between distributions (even of the same family)
and do not forget that the versions of a single windows release are differentiated based on user facing functionality for the most partAnd do not forget that for Windows it has "Home", "OEM", "Professional", "Small Business", "Enterprise" and "Sellakidney" versions, which you can support.
since if you develop a normal application you usually target system-, or installable framework- supported APi's rather than "versions" or specific "features" (except maybe in the case of a specialized / administrative tool intended to interact with one - say, an AD console) for intents and purposes of application deployment they can be considered one thing
except that if your market is windows you can cover it all with as low as one codebase / code path (in the case of a .net application) or at most a couple or three (DX9/DX11, or pre/post vista as far as certain other api's - say, directwrite, or xaudio, are concerned, or...)You do not have to, but then you do not have to support all Linux distros, right?
while if your market is linux you'll have to support all distributions (apart maybe from exotic niche-in-the-niche ones) not to miss on relevant slices of linux' desktop share - and you have to support at least major ones individually (now, it wont probably take N times the whole codebase, but specific if's or#ifdef's will be needed at very least )
Last edited by silix; 09-01-2014 at 05:14 PM.
Last edited by sdack; 09-03-2014 at 04:42 AM.