>>> [EMAIL PROTECTED] 09/29/05 9:46 AM >>> > > Paul, > > <sigh>
Oh boy, here comes the drama... > I think you're looking at this from the point of view of > someone who loves the device, and can't see it's flaws > - not from the point of view of someone who is evaluating. I can see the flaws, and I've chosen to deal with the ones I can control... > I frankly don't care if it's open source or not. I care about > how it interoperates with other devices. My sb and slimp3 interoperate just fine with my stereo and TV. My mediamvp interoperates not only with another TV, but another piece of software I'm running on my server. > I care about how it works in the palm of my hand, or on my > shelf. I care about how flexible it is - I don't want to be > tied down in terms of what I use the product with. I don't see this as being a problem. I have TelCanto and it works great in the palm of my hand. It also works great at work, because I no longer have to bring CDs back and forth - I just listen on my work PC from slimserver all day. That's way more than I could hope to do with any other product. > Whether it talks to a server which is open or closed > source is irrelivant - as long as I have a standard method > of interaction (UPnP, whatever), I have other options available. To me it's as important as DRMed CDs. I've returned 4 CDs in the past month - after they have been opened - because they are not CDs, but music discs. A CD needs to adhere to a certain standard - the redbook standard. upnp is just one method of interaction, there's also CLI and http as well. > Take programming for example: I don't care what C > library I use. I usually don't care what kernel I run. > I have a standard API that I get to use. I can move > my code from NetBSD to Linux to FreeBSD to AIX to > Solaris with minor to no difficulties as long as I conform > to the common APIs. I don't care if the kernel is open > source (NetBSD, Linux, FreeBSD) or closed (AIX, Solaris). I do, because if I discover a problem with the kernel, I have the capability of fixing it...not that I have, but the option is always there. > The API is the common contract. Valid point. > Squeezebox2 has no such common contract. The sb2 doesn't, but now you're mixing hardware and software again. > I'm a programmer who doesn't want to work at > home. I just want the thing to work. And Squeezebox2 > doesn't in my case. I am too, yet I don't mind doing a little at home as well. Sorry to hear the sb2 doesn't work, but I've not seen any postings related to technical problems you've had. > And I have no alternative but to use something else. The way you see it, sure. A Sonos is just a PC with a totally closed piece of software, some music clients and a very fancy remote control. SB2 is a piece of hardware, similar to the Sonos clients. If you don't want to tinker, get an mp3beamer. It's based on slimserver and blows the doors off of Sonos. TelCanto is software that runs on a handheld, similar to the Sonos remote. If things "just work" for me, my engineering background tends to take over and pull it apart to figure out what is making it just work. I figure I'll skip that and just put it together from the start so I know why it just works, which is what slimserver does for me. Obviously, YMMV. > Thanks for your opinions. It's just a shame that you seem to have made up your mind and haven't really said what technical problems you're having. Then again, if you'd be more happy going with Sonos, at least you seem to have given the squeezebox a look. Paul _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
