Tiny cheap solutions like the raspberry pi are kind of limited.

I've got an Intel Atom/NVidia ION mini ITX board that was pretty cheap. It has a single PCIe x16 slot and 4 SATA ports and was worth less than $100. There are similar chipsets which I'm sure would work equally well and still beat the crap out of tiny boards like R Pi.

It's a file server, a media center, and it even does well with office suites and web browsing. Media players like XBMC are no problem, as are standard peripherals like wireless keyboards. I can also drop in up to 4Gigs of RAM and some 12TB of hard drive space.

Way, way way more flexible than any ARM device on the market could possibly be, and much more mature and easier to get working for multiple common tasks - not just playing media.

It's not about HFCS directly. It's the fact that is has trace amounts of a pesticide in it - pesticide that's intended to kill insects!

Now, I admit that I didn't fully read the article, but I'm pretty sure you're missing something fundamental. Monsanto GMO is not directly a problem. The problem is dumping pesticide on things because the crops have been given GMO resistance.

Gee - feed something with trace amounts of bug killer to bugs and it kills bugs. How did no one think of this earlier???

Ok then.

Just scrap wind turbine subsidies and instead propose to build more CANDU reactors in the backyards of the complainers.

They must support that, given than Ontario is mostly powered by nuclear and hydro already.

It seems to me that people blame cheap memory and making larger buffers possible for this problem, but no - if there is a problem, it's from bad programming.

Buffering serves a purpose where the rate of receiving data is potentially faster than the rate of sending data in unpredictable conditions. A proper event driven system should always be draining the buffer whenever there is data in it that can possibly be transmitted.

Simply increasing the size of a buffer should absolutely not increase the time that data waits in that buffer.

A large buffer serves to minimize potential dropped packets when there is a large burst of incoming data or the transmitter is slow for some reason.

If a buffer actually adds delay to the system because it's always full beyond the ideal, one of two things is done totally wrong:
a) Data is not being transmitted (draining the buffer) when it should be for some stupid reason.
b) The characteristics of the data (average rate, burstiness, etc.), was not properly analyzed and the system with the buffer does not meet its requirements to handle such data.

In the end, it's about bad design and bad programming. It is not about "bigger buffers" slowing things down.

No, there is no audible difference between 44.1kHz and 192kHz if all you want to do is listen. However, if the intent is to do any post-production work, re-mixing, mash-ups, whatever - then the quality makes a big difference.

Try running time-shifting or pitch-bending (not dumb-resample where time and pitch both change), and I assure you, you'll get much cleaner results starting with the 192kHz file.

Stop thinking of "desktop PC's" and start thinking embedded hardware products. Tons of things are moving that way anyway.

In general, I find that the embedded community is much more into open source solutions.
Windows is the king shit desktop OS. Linux is the king shit embedded OS.

The ability to be picky with online dating is the whole point! You can put all of your cards on the table before ever even meeting someone. In this busybody world, people don't want to have to go through traditional dating, only to find out months into a relationship about some strong deal breaker like wanting kids. That's just a disappointing waste of time and people are starting to realize it.

If you're looking for someone to spend your life with, you damned well should be picky. For the record, I met my partner online many years ago on a niche dating site, so maybe I'm a little biased.