Of course, they suck for completely different reasons, which is part of the frustration. And each have places where they shine. Why can’t there be a nice combination of all three? That would be perfect.

Why Mac OS X sucks:

• Apple is becoming a controlling, closed system, and with the advent of the Apple App store, developers have to go through an approval process to get their apps on the store, there are specific things you can’t include in an app in the store, and there will come a time when most people get their software through the store, so there will be less and less incentive to maintain non-app store versions of software apps
• These days, you can find most kinds of software for the Mac, but there still is a relative paucity of apps in comparison to Windows.

Why Windows sucks:

• Viruses, Trojans and Worms, Oh My!
• Although I have only seen the Blue Screen of Death once in my year of Windows 7 use, there are still inexplicable slow-downs, crashes, and weird problems. And it takes FOREVER to boot, even with Soluto.
• Internet Explorer

Why Linux (in my case Ubuntu) sucks:

• I have to go through arcane (and luckily for me, fairly painless) procedures to get simple things to work (like plugging a headset with a mic into my jack!)
• Hardware manufacturers ignore Linux for the most part
• Most software developers don’t make Linux versions

The only good news I can see is that the operating system is getting less and less relevant. And, on balance, for me, Linux is winning. Now that dropbox and scrivener work on Linux, and I’m moving from Quicken to some online cloudish thing (suggestions?), I can pretty much leave Windows behind. (Oh, there is still Netflix. Sigh.)

On the proprietary side, there are two options. Proprietary Unix, and Microsoft Windows, and associated Microsoft Software. The current version of MS Server in use is Server 2008. Microsoft has web server software called IIS, and it’s database server product is MS SQL server, which people use for far more than just serving web site data. The primary web development framework used in this environment is .NET.

Proprietary UNIX has dwindled greatly in popularity with the increasing popularity of Linux. On top of proprietary UNIX, people will generally run associated open source server software for web, database and development frameworks.

On the open source side, Linux is by far the most popular, with BSD in second place. Both Linux and BSD come in several flavors (or distributions.) Apache is by far the most popular web server software. MySQL and PostgreSQL are the open source database systems most in use for web servers, with PostgreSQL being a pretty distant second to MySQL. Other database systems (such as NoSQL variants) are increasing in popularity, but are pretty far down from MySQL as well.

Also, it is possible to run Apache, most varieties of open source databases and web frameworks on Windows, and that is not uncommon.

It’s hard to know what the market share of server operating systems are, because there are different ways to measure it. You can measure how many units are sold. By that measure, Windows is first at about 49-67%, Linux is second at 16-23%, and proprietary UNIX is third at 7-22%. That underestimates things like self-installed OS systems (standard with Linux), as well as VPS systems. If you measure by surveying publicly accessible websites, you get Linux first at 41%-74%, Windows second at 20-42% and proprietary UNIX third at 2-5%. This underestimates servers inside enterprises. (source: wikipedia)

From my perspective, the underestimation of self-installed and VPS systems by the first measure far outweighs the underestimation of enterprise servers, because plenty of organizations and enterprises also install Linux behind the firewall. It would make sense to me that the true number is much closer to the estimation by publicly accessible websites, rather than the unit sales estimation. So on the OS side, Linux does look like it wins.

Apache is far and away the most popular web server software. It is way ahead of IIS. The most recent data from Netcraft shows that Apache has 63% of web servers, compared to 19% for IIS. Also, Apache is showing a clear upward trend, and IIS a clear downward trend.

I’ll start with basic graphics – graphic manipulation tools. Of course, on the proprietary side is the ever present and predominant Adobe Photoshop and Illustrator. And, honestly, they are very good tools, and considered industry standards.

On the open source side, the projects that stand out are GIMP (a Photoshop replacement) and Inkscape (a vector graphics program – like Illustrator). I’ve used GIMP for many years, and I don’t generally do a whole lot with graphics, but it always serves my needs.  There has been a lot of back and forth about the GIMP user interface. It is very unlike that of Photoshop. So much so, in fact that someone came up with another project called Gimpshop, which re-does the UI to better match Photoshop.

Both GIMP and Inkscape are completely cross-platform, and available for Mac, Windows and Linux. I’ll leave it to the graphics professionals to say for sure, but they are both worth a look if you don’t want to plunk down hundreds of $ for Photoshop and Illustrator, and/or you like to work with open source tools.

The other realm of stuff that I know some about is video. In term of viewing, on the proprietary side are the players that come with the proprietary operating systems. Itunes/Quicktime comes native with MacOS, and Windows Media Player for Windows. One doesn’t have to pay for these, so it’s a bit hard for open source (or other products, even) to compete. Which is perhaps why the other major proprietary video player, Real Player, has had such a hard time catching on for all of these years. I notice now they seem to have added a ton of features (like video conversion from one format to another).

On the open source side, one program you must know about is VLC by VideoLAN. Totally cross-platform (so cross-platform, they have a version for BeOS!) It plays everything. I mean, everything.This means you don’t have to have several video players around to play different formats. I use it constantly – it’s my go-to video player. It has a bunch of other features as well.

In terms of video editing, again, the proprietary programs have somewhat of a leg up on the open source, although a recent entry into the field may well change that (see below). On the “low-end” (for people like me who make videos like this,) there is, like in the video playing arena, iMovie and Windows Movie Maker, made by Apple and Microsoft respectively, for their own platforms. (An aside, a lot has been said about the crapware iMovie has become – it used to be a really good video editor.) There are other proprietary products as well. I’ve used TrakAxPC, which has a free version and a paid version. There are a variety of other low-end video editing options. There are low-end versions of Adobe’s Premier (called Elements) and Apple’s Final Cut (called Final Cut Express.) On the high end (where I’d love to work more), there is Apple’s Final Cut (only available on Apple hardware) and Adobe Premier (cross-platform). There are also quite a number of high-end, Hollywood products, like Avid (a side note, I used Avid a little bit, way back when it was the first and only non-linear video editing platform).

On the open source end, there are some notable entries. Blender is a very popular cross-platform open source 3-D modeling, animation and editing tool. It’s actually pretty amazing what it can do. (There is a study that compares a bunch of 3D tools for professionals, you can see how Blender stacks up.) Another notable entry is Cinelerra, which only runs on Linux. (You can see videos edited with Cinelerra on Vimeo.) A recent entry into the fray, and the one that might make a huge difference, is Lightworks. This is one of the video editors that Hollywood uses that used to be proprietary. It will go open source later in the year, but you can grab it for free right now. Yes, a Hollywood-quality video editor for free, and soon to be open source. It’s Windows only for now, though.

In summary, proprietary software has the popularity edge, mostly. From this non-graphic professional’s perspective, it seems that one would not be left wanting if you went the open source route, however.

I’m going to focus here on the nonprofit sector, and options that are most common among nonprofits.

On the proprietary side, there are a number of options, and they fall into three categories:

1. Single-source proprietary custom CMS (from one web shop, or web host)
2. Proprietary CMS as part of a large package (such as from Convio or Blackbaud)
3. Proprietary stand-alone CMS (such as Sharepoint.)

You already know what I think about option 1, so I won’t belabor it here. Many people have found that option 2, using a large package, which includes donation pages, event management, etc. can be a really good option, and I certainly don’t want to say that this is not a good idea – I think it can be – but it also can be quite costly – and for many organizations, it’s overkill. And there are open source options that can do much of the same work for much less money.

There are not a lot of stand-alone proprietary CMS systems in nonprofits these days. Microsoft Sharepoint might be the most common I’ve heard of. Ektron is another one that I’ve heard folks talk about, as well as ExpressionEngine. The advantage of using Sharepoint for Microsoft-centric shops is that there is full integration with lots of internal network resources.

The open source options are many, but the big four: WordPress, Drupal, Joomla, and Plone, stand out from the pack. As you know, I am pretty loyal to Drupal (and secondarily, WordPress) but I have to say that Joomla and Plone are solid, wonderful projects, with great communities, and active development, and will serve you well. Check out Idealware’s newish comparison of the four – it can help you figure out what’s best based on your needs.

Other open source options that I think are worth looking at include: Alfresco, which is heavy on the document management functionality and DotNetNuke, which is based on .NET, and somewhat popular among Windows users. Two up and comers I am very interested in following include Radiant and Refinery, both based on Ruby on Rails. There is also Django-CMS, written on top of the django framework (a python framework.)

If you’re really interested in open source CMS options, and looking not for data on features, but for data on popularity, marketing, community and such (a good idea if you are, for instance, a shop deciding what CMS systems to develop with and support) check out this report from Water and Stone (a digital marketing agency.)

I think on the whole, though, the number and richness of options on the open source side is quite a bit better than that on the proprietary side, and until I get an answer to this question, I can only guess that open source options have won over proprietary ones in the nonprofit sector.

At the moment, if you want to integrate Drupal and Salesforce, you have three options:

1. Use the contributed modules (or have a developer install and configure them for you).
2. Use Jackson River’s Springboard.
3. Roll your own (or have a developer roll your own for you.)

I’m going to talk in much detail about #1 in a bit. I’ve not had any experience with Springboard, but it’s important to understand that it is not open source, and is only maintained by one shop. That is going to be an inherent weakness – no matter what. I don’t know enough about it to match it to the contributed modules, but it’s hard to imagine that it’s possible for it to keep up, given the nature of open source development. All of that said, it’s supposed to be an interesting all-in-one sort of option, so it’s probably worth a look.

Rolling your own is always a precarious proposition. I frankly can’t imagine much of a situation where  it would be preferable to modifying what’s available and contributing the mods back.

So what is the status of the Drupal modules? Right now, there is an alpha release for Drupal 6, which is alpha in that very humble open source sense – it’s being used in quite a number of production sites. It includes some great stuff. You can see an overview here, in the slide deck for a talk given at NTC last week, which compares the integration of Salesforce with 3 of the big open source CMS platforms, Plone, Drupal, and Joomla.

There are four major projects:

• Salesforce Suite, which includes:
  • The API – the core module that does the communicating with the Salesforce API
  • Contrib – a module that provides support for import/export from contributed modules
  • Export Queue (experimental) for queuing exports
  • Import – importing data from SF
  • Match – for matching objects before creating new ones
  • Node – for linking Drupal nodes to SF objects
  • Notifications (experimental, sort of – it’s worked quite well for me) – allowing Drupal to handle SF outbound messages
  • User – matching users to SF objects
• Salesforce/Ubercart – provides integration for Ubercart. Uses the Salesforce Suite API
• Salesforce Feeds – allows for feeding SF records into Drupal via Feeds. Also uses the Salesforce Suite API
• Salesforce Webform – Allows for passing data from a Drupal Webform to Salesforce. Currently does not use the Salesforce Suite API, and cannot be used on the same site as the Salesforce Suite, but hopefully that will change soon.

All of these modules are actively maintained, there is an active base of folks using and contributing (including me) and there are plans afoot for Drupal 7, with big improvements. Of course, there are still some snaggy spots, and it helps if you know some about Salesforce to have this work really well, but I’ve gotten good results doing two-way sync of user and node data with the Salesforce Suite, as well as used the Salesforce Feeds module some.

If you use Salesforce, want integration, and are pondering a CMS choice, definitely check out the overview slides. If you are using Drupal, want integration, and considering a CRM, definitely consider Salesforce. And if you are already using both, and looking to find ways to integrate them, drop me a line, I can either directly help you, or point you in the direction of folks who can.

And, in my experience over the past 15 years, it’s where organizations are willing to spend the most money on technology – often more than on their website or other technology tools – for good reason. Because of this, the deck has always been stacked against open source tools in this arena. The sheer number of vendors providing this toolset for nonprofits is huge (although rapidly shrinking.) Two of them (Convio and Blackbaud) are even publicly traded companies, which says a lot about the profit potential of this vertical.

On the proprietary side, there is a wide range of available tools, from the relatively inexpensive, like Salesforce (web-based, including Convio Common Ground and the Nonprofit Starter Pack,) eTapestry (web-based, now owned by Blackbaud), Democracy in Action, and GiftWorks (desktop) to the egregiously expensive (you know which ones I mean.) Both NTEN and Idealware are the best sources for information about the range of options for this toolset – that’s out of scope for this post.

As you can tell, I’ve lumped SaaS tools like Salesforce, DIA and eTapestry in with proprietary in this post – that’s because that’s what they are – proprietary. However, Salesforce in particular has a leg up that most other proprietary tools don’t have, because of their open APIs and their incredibly robust development platform. That combination is impossible to beat if you need integration, ease of data movement, and a lot of customization. From my perspective, open data (via open APIs) can sometimes be more important to consider than whether or not a tool is open source – since integration with other tools, as well as using external tools of various sorts is critical. Closed data systems, difficult to integrate systems, or systems that require payment to get access to your data should be avoided at all cost.

On the open source side, there are a number options: you can choose an open source CRM package (designed for business), like SugarCRM, and use it or customize it for use in a nonprofit, use CiviCRM, or choose the desktop-based nonprofit CRM called MPX (built by a company called Orange Leap.) I’m excited about a new Drupal project called “Red Hen CRM” but it’s very fledgeling.

CiviCRM is a web-based open source nonprofit-focused CRM/Donation management tool. It’s been around for a while now, and is used by many organizations, some quite large (like the Wikimedia Foundation.) It is quite broad in its feature set – it has donation pages, event management, e-newsletter functionality, even a case-management system. I’ve installed, configured and administered CiviCRM many times, still work with it, and I have, like most developers, a love/hate relationship with it:

• I love that it’s open source/free software
• It’s got a great community of developers and users
• I love that it’s feature rich – you cannot find the whole set of things it does in any proprietary tool that I’ve seen.
• It is a tool that has unmatched cost-effectiveness for small organizations
• It’s great that it integrates with both Drupal and Joomla (although the Drupal integration is by far the most solid – and it is a very nice integration – hard to get with proprietary tools.)
• It is relatively easy to set up for most functionality

But …

• Data migration into CiviCRM is often nightmarish (this is really where the hate lies)
• Reporting tools are improving, but don’t match the proprietary versions
• It can sometimes be pretty tough to handle complex issues
• It can be tough to troubleshoot issues

MPX is a desktop tool, and although it is open source (GPLv3,) unlike CiviCRM, or SugarCRM, it is built on top of a proprietary stack (.Net/MS SQL Server.) It has primarily been used in faith-based organizations (that is Orange Leap’s primary client base.) But it’s a very full featured product, and quite mature.

So if you are a small organization that perhaps is still working with spreadsheets, CiviCRM is a great idea to check out. But in general, there are a lot choices and, sadly, few of them are open source.

So what does someone do who builds their houses right on top of the LAMP stack (M standing for MySQL)?

For most folks, especially if they build on shared hosting infrastructures, this just isn’t an issue. They depend upon their hosting providers, for whom it may or may not be an issue – but they won’t have to think about it. For those folks in a position to choose which database software to use, (for example, you use VPS systems like Amazon, Slicehost, Linode, etc.,) then I think there are two pretty good options:

• Go with MariaDB, which is basically a drop-in replacement for MySQL (and conveniently starts with an “M”.)
• Switch to PostgreSQL.

MariaDB is a branch of MySQL that came about because of the uncertainty relating to Oracle’s ownership of MySQL. From the website:

In most respects MariaDB will work exactly as MySQL: all commands, interfaces, libraries and APIs that exist in MySQL also exist in MariaDB. There is no need to convert databases to switch to MariaDB. MariaDB is a true drop in replacement of MySQL! Additionally, MariaDB has a lot of nice new featuresthat you can take advantage of.

The problem is that the major Linux distributions (Ubuntu, Debian, RedHat) don’t yet have MariaDB in their repositories, so it will be a while before MariaDB is an easy apt-get or yum away from installation (there are some independent repositories and builds.)

PostgreSQL is a different beast entirely. It’s been an also-ran in the open source database race, and I was, for many years, quite faithful to it. It’s a very solid database, and it was ACID compliant before MySQL was. It’s major weakness (and why the LAMP stack is called that and not the LAPP stack) was that it was a fair bit slower than MySQL. But  that weakness has long been taken care of, but the damage was already done.

Many open source web database systems can use PostgreSQL instead of MySQL at this point. But PostgreSQL doesn’t have the same large user base, and doesn’t have many of the same web-based and desktop tools that MySQL does. There are differences in the SQL commands and such, and the command-line interface looks different. There is also a big difference in how Auto-numbered fields get handled, but that’s not really an issue that folks who don’t dive into deep database and code need to deal with.

So which to go with? It probably makes sense to wait a bit, first for MariaDB to make it into mainstream repositories, etc., and also to see what the fate of MySQL is. And checking out PostgreSQL is always a good option, it’s a very good database system, and the likely flight from MySQL might do the project some good.

On the proprietary side, still, sits Internet Explorer, now about ready to pop with version 9. It definitely depends on who is gathering the data, but IE has about 44% of the market. This is down significantly from its high point, back in the dark ages of 2005, when it garnered over 90%. It has been dropping steadily since. This drop has been primarily, but not exclusively due to the open source browser, Firefox. More recently, however, two other proprietary browsers, Opera and Safari, have been increasing their own market shares. Now, Opera gets about 2% of the market (up from microscopic some years ago.) Safari, used mainly by Apple Mac users (although there is a Windows version) now gets about 5% of the market.

On the open source side, Firefox is certainly the leader, with a bit less than 30% of the market. Chrome, which is sort of an open source browser, is now getting around 14% of the market. So what do I mean when I say Chrome is “sort of an open source browser”?  Chromium, is the open source project which results in the browser Chrome – but there are a bunch of additions Google makes to Chrome which are proprietary, and not in the Chromium codebase.

So, anyway, basically, between Firefox and Chrome, the open source side is a smidge in the lead over the proprietary side, but it’s pretty close to even. And still, the primary reason for the difference is that IE still ships with Windows (and Safari with Mac OS X), and if people don’t take the step to download and install another browser if they are a windows user, they will still just be using IE.

In the mobile space, things are very interesting. Opera mobile is in the lead, with about 21%, followed by iPhone, Nokia, and Blackberry. These are all proprietary. Bringing up the rear is Android, at 16%. But I’m sure that is going to change as Android begins to gobble up the moble smartphone market share.

I’ve been using this tool since it actually was StarOffice, more than 10 years ago, when it was first open sourced by Sun in 2000. For most of that time, except when I was doing heavy collaborative editing with colleagues who are using MS Office, it is my Office Suite of choice. There have been many times, over the course of the years, where there are things I’ve thrown at OpenOffice.org that it couln’t handle, but those things have diminished year by year, and over the past couple of years, I’ve had absolutely nothing to complain about (nor have I submitted any bugs, which I did a fair bit of in the early 2000′s.)

I would take a bet that 90% of people who use MS Office don’t need to pay for it, but can do fine with OOo/LO. 70% of people could pick up OOo/LO and use it with no training or help, even if they are used to MS Office. It is the only fully cross-platform office suite with pretty much the same functionality and interface independent of platform. It reads and writes all MS Office formats (except for Access files.) It does have a drawing program, an XML editor, as well as a math equation editor, in addition to the standard word processor, spreadsheet, presentation tool and database. Oh, and did I mention it’s free as in beer, too, instead of adding a couple of hundred bucks or more to the price of a new PC?

So what are it’s weaknesses?

• The spreadsheet doesn’t yet have all of the functionality of Excel. It’s pretty darned close, but even I have to admit that Excel is darned hard to beat.
• It doesn’t have The Ribbon I think most people would say this is a strength. :-)
• The presentation package isn’t quite as polished as PowerPoint, although you can do most of what you can do with PP.
• It doesn’t have Publisher
• The database has not come anywhere near the functionality of Access.

The days when many a nonprofit were run by Access databases is coming to a close as things move more and more to the cloud. Google docs will take a good long time to make it to the point where the functionality begins to match either MS Office or OOo/LO, so OOo/LO is a very good alternative to MS Office if you don’t need MS Access, and have folks able and willing to make a small adjustment to use this tool. I know that the fact that nonprofits can get MS Office for $30 or so makes a change unlikely, and I’ve carped about that one for years. But at least, for now, it seems that MS is still willing to be generous.