Why you should support Mac OS X and Linux
blog.wolfire.com
blog.wolfire.com
I'm dealing with this with tarsnap right now -- I know the code works on FreeBSD, NetBSD, OpenBSD, OS X, and OpenSolaris; but for Linux all I can say is that it works on Debian, Ubuntu, CentOS, Slackware, Gentoo, and RedHat. Does it work on SUSE, Mandriva, Xandros, MontaVista, or Linspire? I don't know. (But if anyone here runs any of those, I'd be happy to hear from you.)
Yes, I could install N different distributions of linux and test them all; but testing on N different distributions is much more work than testing on 1, and many people simply won't have the time.
- architecture (usually i686 or x86_64)
- availability of the right library versions in /usr/lib (however, you can combat this by "shipping" the versions you need with your app)
- (rarely) kernel version
- (even more rarely) glibc version
In other words, most of the time, if it's an Intel binary, it seems to work pretty well.
If a particular Linux distribution seems necessary, it usually just means that one of the above features of that distribution is important.
http://www.rpath.org/ does something like that for server side software, and I know vmware supports that model.
* varying definitions of off_t (fortunately autoconf fixed this for me).
* the linux 2.4 kernel returning EINVAL for the interaction of TCP_NODELAY and TCP_CORK (fixed by avoiding the problematic interaction on all linuxes).
* the header files for openssl, zlib, and ext2fs/ext2_fs.h sometimes being installed and sometimes being part of packages with a wide variety of names (which I'm attempting to work around by providing a list of "the package you need should have a name something like this...").
I think there was a library version issue at one point too, but I can't remember what it was.
Yes, I could avoid problems with header files if I only provided binaries; but even leaving aside the question of security, this would mean that I'd have to deal with the problem of packaging binaries in N different ways.
Another approach may be to use autopackage or similar.
Also, consider that the major Linux ditros have far more users than the different BSDs or Solaris do (OK, there's a lot of old projects running Solaris, but it's very rare to pick for new projects, so I doubt this would be a big source of customers for new software).
This forced us to bundle the Sun JRE with our application on Linux, which effectively doubled the size of it. It was worth it though because we haven't seen any Linux incompatibility issues yet.
(ps: I can test tarsnap on ArchLinux)
Sorry, but that doesn't sound very sane to me. :)
Windows is a far larger market, so early adopters and trend setters aren't as loud as they might be in an empty room, but that doesn't mean there are less of them. Instead, they tend to be visible only in niches of the PC market, rather than simply the Mac niche or FOSS niche.
Also, I recommend that you moderate your intake of propaganda re Windows security too. Windows is the big target, and has by far the largest number of suckers (i.e. unsophisticated users). That doesn't make it inherently insecure, or savvy users of it incompetent.
Since we are in a technical niche (network security) a lot of the traffic to our site is from Linux and OS X users, but 85% of it is still from Windows. It's painful to watch people arrive at our site, realize in the first 30 seconds that there is no version of our software for Windows, then disappear (probably forever).
Windows Vista was the first Windows consumer OS to ship with a firewall enabled, and that by default used limited privilege accounts that prompted to elevate privileges when needed.
When did Linux and OS X have those features?
Vista was the first Windows OS to ship without inbuilt, unfixable windows-smashing vulnerabilities. Did Linux or OS X ever have an equivalent unfixable vulnerability baked into the display server?
How long has the idea of all software being digitally signed been in the Windows world?
How long has the idea of 'it's compromised, game over, reinstall and re-apply non-executable data if you think that's not compromised too' been around in the Windows world? Or do people still use 'anti-virus' software as a line of defense, when it's already too late?
Which current consumer version of Windows has mandatory access control ala SELinux or AppArmor?
Which version of Windows has chroots? Process jails?
How large is the 'Windows Hyper V appliance' based on Server Core 2008 compared to VMware ESX3i?
Which OS requires users close all their application, stop executing their kernel, and restart everything for simple, non-kernel updates?
With your answers to the above in mind, do you think you should perhaps limit your own intake of propaganda regarding Windows security?
The statement "people who run Windows are generally not trend-setters or early adopters" remains true, and is actually supported by what you said. Also, the poster did not refer to Windows users as "suckers" or "incompetent", or describe Windows as "inherently insecure", so you should consider the possibility that you've misunderstood the intent of the message before accusing him of "hubris", "bigotry", and being a consumer of "propaganda".
I was about to recommend that he take a look at Tarsnap, until I saw it doesn't support Windows.
He definitely also meant it's easier to dominate a smaller market with less competition than a be a medium player in a big market.
"The team focused on the Macintosh platform, not Windows-based personal computers, because the Mac market was more open and Jones had been raised on the platform."
http://en.wikipedia.org/wiki/Bungie#Founding
They had a clear and open field making quality games exclusively for the Mac platform, and this brought them a devoted following and a steady flow of profits. They later branched out into Windows, and of course Microsoft bought them out so they would focus predominantly on the XBox.
So, while ignoring Windows indefinitely may not be a great strategy, ignoring it at first can be.