I must be missing something here. If I am approaching this wrong just ignore my whole post. And also this isn't posted directly at the OP here, just in general to the thread. I apologize in advance for the rant.
The Raspberry Pi is a hardware platform based on the Broadcomm SOC. It's awesome that they got all of this on a small form factor with some options that make this available to a wider audience (outside of classroom programming environments).
The (majority of the) software that runs on the RPi is open-source and publicly developed from someone who does it as a hobby. Each program you install on this hardware is developed by a separate group of maintainers spread throughout the world. Having a problem with Chromium? Visit their site (http://www.chromium.org/Home
) and submit a bug report. If omxplayer is having a problem try to reach the developers with a bug report (https://github.com/huceke/omxplayer/issues
). Wish program XYZ could be installed on the RPi? Go to their site and ask for ARM support. Think that vim is the greatest thing since sliced bread (which it is btw), go to the vim site and click the donate button.
There are exceptions to this rule though, companies like Red Hat and Google have full time developers on staff to support freely available open source software. However I would be willing to go out on a limb and say that most companies don't have that. When my RHEL box at work decides it doesn't want to launch Firefox anymore I don't go to my boss and say that we need to hire a Firefox developer to fix my issue.
One of the really great things about this as well is it is getting a lot of people that couldn't spell Linux to install it at home and learn new things. The FOSS (Free and Open Source Software http://en.wikipedia.org/wiki/Free_and_o ... e_software
) community will definitely grow due to this and that's just awesome. However it brings with it people that are new to that arena and aren't used to products not developed solely within one corporation. This is a dramatic change in mindset.
If the RPi has an issue caused by hardware it would be within their realm to try to get it fixed (or to rally the open source community to help them do it). With any new uses to hardware there are going to be growing pains, but the rapid development cycle most of this software is going through will help ease this pain a lot.
I haven't really used the RPi for it's intended purpose either (XBMC is awesome), but if there was a problem with the core functionality I am sure they would pitch in their own man hours to resolve it. I am positive that the RPi guys did do a lot of work to get software ported over and compiled for the RPi, but to blame them for software ABC not working is a bit of a stretch.
I will try to avoid future rants