I use a Roku (ha!) soundbridge for my music :-) But I only really use it to stream. For my own collection, I just use my phone or mp3 player directly.

Check out the wdtvlive plus. It plays pretty much any file format I've thrown at it, and can mount drive shares, or just use a media streaming server. Its internet stuff is ok, but that's not what I use it for.

Another vote for the wdtv live (I have a few plus models). It plays everything you throw at it, and can use network mounts or a streaming server. You can even use an alternate firmware to host a web server, torrent client, NFS mounts, etc. Not sure if it is still being maintained, and for my use, the stock firmware works great.

With a good antenna, OTA is really nice these days. Unfortunately, most new tvs no longer include it, but ota also includes an episode guide.

Rather than spend money on a tivo, look into the homeworx or iview units. $40 for a digital tuner that acts as a pvr with your own USB drive.

I also use kat to catch other things. I'd pay for a similar service if it were available, but alas it is not, nor will it ever be.

Being creative is fine, but being creative while improving how things are done vs. the opposite is much better.

The big problem used to be the media companies paying the radio stations to play their artists music...

The terrorists won.

rhel-only shop, I've had good luck just packaging my own stuff and using yum with my own repositories. Then keeping each server up to date is a simple matter of 'yum clean all & yum groupupdate whatevergroups'

Like javascript? 1+2 = 12?

If you are not going to have strong types, then you must use a different operator for string concatenation vs. math. The above is one reason I can't stand javascript.

I'd be down for making it illegal, but they need to legalize pot.

Exactly. You are treating the effects, not the disease itself.

If Android could inherit much of what makes WebOS great, I would be ecstatic!

But you only ever need ONE COOKIE, and it only needs to be a nice little session ID. Imagine that. If you are sending data back and forth via cookies, you are doing it wrong.

Of course, HTTP allowed us to use a single program to access all kinds of content. Seems with phones, we are going back to the model of writing a client for every thing you want to do. Just that it all uses the same port to do it now.

Being the guy who has to say no sucks. Worse if you have none of the authority and all of the responsibility when things go to poo.

But it didn't survive the market well.

It was called WebOS. Some people still cling to it, but it's a dead platform.

Didn't like the way things looked or behaved in any app? It's all CSS and Javascript. Patch it. Patching WebOS was a very nice, elegant, and easy way to customise the phone.