One of the great features of the Squeezebox (and the recently announced Sonos) is that you can sync multiple devices together and have the same audio playing around the house, regardless of location. There are other ways to do this, of course, but it'd be great to be able to do the same with the Airport Express.
The WWWW (World-Wide Web Worm) pre-dated WebCrawler (and Jumpstation pre-dated it.) Jumpstation indexed only titles, while the Worm indexed both titles and anchor text (IIRC).
A number of posters have raised the question of why building your own is worth it. There are a number of great reasons (and FWIW, I own a TiVo and love it):
1) It's likely that you can get some of the features you want more quickly by using something based on open source. If it doesn't have what you want, you can just add it!
2) The idea of having the people that produce or distribute the content having any control over how it's watched really annoys me. It's my TV, and I'll watch it the way I want. Does this happen? You bet: DirecTV controls the features that get added to your TiVo at home.
3) You can archive everything. Hard disk space is really cheap. It's pretty easy to imagine a huge collection of movies that you just skim from your feed. Sure, you can hook a PVR up to a recordable DVD, but you really want this to be built automagically.
4) Nobody's monitoring what you watch. Sure, TiVo has a nice privacy policy, but the fact that such info is even collected scares me.
It's the set of libraries that will really take time to learn. Seriously. An int is an int in Java, C, and Obj-C. But how do you structure your application? What call do you make to turn your window blue? And what's the right way to get text to show up in the typeface you prefer (or better yet, in the typeface the user prefers?)
Answering any of these questions depends on the API you choose to use. If you know Swing already then you'll get bits on the screen a lot faster than if you decide to learn Obj-C and all the Cocoa Frameworks. On the other hand, if you're starting from scratch on all of them and you don't have any portability concerns then go for Cocoa -- you'll get going quickly and you'll love the result.
Slashdot Mirror
One of the great features of the Squeezebox (and the recently announced Sonos) is that you can sync multiple devices together and have the same audio playing around the house, regardless of location. There are other ways to do this, of course, but it'd be great to be able to do the same with the Airport Express.
The WWWW (World-Wide Web Worm) pre-dated WebCrawler (and Jumpstation pre-dated it.) Jumpstation indexed only titles, while the Worm indexed both titles and anchor text (IIRC).
... to try to get one of these things through airport security, to say nothing of the 5 replacement cartridges I'll be carrying in my briefcase.
A number of posters have raised the question of why building your own is worth it. There are a number of great reasons (and FWIW, I own a TiVo and love it):
1) It's likely that you can get some of the features you want more quickly by using something based on open source. If it doesn't have what you want, you can just add it!
2) The idea of having the people that produce or distribute the content having any control over how it's watched really annoys me. It's my TV, and I'll watch it the way I want. Does this happen? You bet: DirecTV controls the features that get added to your TiVo at home.
3) You can archive everything. Hard disk space is really cheap. It's pretty easy to imagine a huge collection of movies that you just skim from your feed. Sure, you can hook a PVR up to a recordable DVD, but you really want this to be built automagically.
4) Nobody's monitoring what you watch. Sure, TiVo has a nice privacy policy, but the fact that such info is even collected scares me.
It's the set of libraries that will really take time to learn. Seriously. An int is an int in Java, C, and Obj-C. But how do you structure your application? What call do you make to turn your window blue? And what's the right way to get text to show up in the typeface you prefer (or better yet, in the typeface the user prefers?)
Answering any of these questions depends on the API you choose to use. If you know Swing already then you'll get bits on the screen a lot faster than if you decide to learn Obj-C and all the Cocoa Frameworks. On the other hand, if you're starting from scratch on all of them and you don't have any portability concerns then go for Cocoa -- you'll get going quickly and you'll love the result.