Nope, it's just a better made CD. Regular CDs aren't exactly problematic though, so it'll probably be one of those things where it gets used on expensive music collections to make people think they're buying premium stuff.
Beast with a Billion Backs was marketed as a fairly dirty (for Futurama) DVD. There were references to tentacle porn right in the ads. I'm guessing it had a bit of crossover appeal from the people who are really into that. I imagine they were disappointed at the rather religious tone in the DVD. Benders Game was solidly aimed directly at Futurama's fanbase (nerds) so it didn't have the crossover appeal.
In my opinion (because everybody on the internet has an opinion) all three DVDs have been good, but not great. Beast was the weakest of the three, but even it had good parts.
The problem with swapping disks constantly is that most drive connectors (don't know about SATA specifically) are really only designed to be swapped a few hundred times at most. The mechanical stress of constantly unplugging and replugging the drive could very well lead to stress fractures in the connector, especially since they're often held on with just solder.
Cruise ship markup on top of satellite provider markup? And he streamed an entire game? Last time I checked, BGAN service was on the order of $7/MB, given that cruise ships are going to mark that up a factor of 10 or so, and assuming he transferred a few hundred megs it's probably about what you'd expect.
It may be a misconfiguration, but it's also the default configuration. Most phones try to lock on to the best signal, preferring to use the native carrier mode first, but defaulting to whoever will give you any service at all otherwise. Manual selection mode is an option you have to enable, usually buried well down in the option menus somewhere. Of course if the guy in the article were smarter he would have wondered what that little icon (roaming indicator) on his screen was before he watched a streaming telecast.
Sounds to me like your sin went beyond posting meta-griping that was almost certainly off topic, but also to carefully avoid posting anything constructive to counteract the Karma loss.
Oil rigs don't store mass amounts of oil though, at least not the ones that have been decommissioned like these have.
Frankly the safety issues are a lot trickier. Oil rigs aren't the safest places to be to begin with, and when you neglect the maintenance for years it can't get any better.
Depends on what kind of phone. I could charge my Blackberry Pearl off of the low power mode, but it literally took all night. Installing the driver let it charge in about 15-30 minutes, depending on how far I ran it down. The phone even put up a warning message that the charging current wasn't sufficient if you tried. For something like an iPhone I suspect it would take hours and hours to charge on low power mode.
On the other hand, I have a bluetooth headset that charges from zero to full in about half an hour off of just 100mA, so this clearly depends on the device.
You have a phone with S-Video out? Anyway, if you have a phone with a bunch of obscure ports like that, wouldn't it be better to have a separate connector for the power/data/digital audio from whatever weird ports you also have? Separate headphone jacks are hardly unique.
Because of the way USB is designed. If your device does not get attached to a driver, it is stuck on low power mode, which is not sufficient for charging a phone. When a driver is attached, the driver can ramp the port up into high power mode and charge the phone. Often times if you know what you're doing you can avoid installing the whole "driver suite" and the crappy apps you don't want and instead just copy over a.dll file to let your computer charge the phone. Google is your friend in these cases.
So the first question that comes to my mind when someone says "solar powered cellphone" isn't "does it have a pedometer", but rater "how long does it take to recharge and how long does the battery last". For some reason TFA answered my first question, but not the second.
Right now I tend to recharge my phone at night because I use it during the day. This could be a problem with a solar powered cell phone. If it's power efficient enough that I can leave it on my desk at work (under standard fluorescent lighting) and keep it fully charged then this could be great. If I have to leave it on a windowsill in direct sunlight for half of the day every day, it's far less practical.
1. How practical is this technology? Could you mass produce cheap low power receivers to put in every car/computer/etc...? How complex is the transmit circuitry?
2. How resistant is this to atmospheric and other interference? In theory it should be pretty resistant, but in practice who knows.
Needing multiple antennas to get this done sounds like a rather big limitation to me.
Unless your shared storage solution was absurdly large TbE is still going to be overkill. Even 10GbE is difficult to sustain without half a rack full of machines. 40GbE is still considered overkill for pretty much anything outside of an internet backbone link. TbE is more bandwidth than you can handle.
TFA specifially says that it doesn't work on encrypted traffic. In fact the whole thing seems to have some rather bogus qualities to it.
It uses a FPGA, but is stuck at a rather pokey 100Mbps. All it does is compare the encoded hash value in the Bittorrent header against a list of known illegal hashes. Hashes you have to program manually.
I've seen commercial boxes that you can already buy that do a lot more than this and faster. He made a big deal about it not disturbing the network, but that's a standard feature. Unless this thing is dirt cheap or something, I don't really see the application.
We can only hope they fired the morons that took over Team Sonic and are forced to look for some less completely retarded people to take over for them.
Big corporation buys some land to put buildings on. Previous occupant happened to be a paper mill, but who cares? Maybe I'm crazy, but I really don't see what's so newsworthy about this.
It's not so much contempt as it is inertia. We spent the better part of a decade getting all of these various applications working on Linux, and nobody wants to go back to square 1 with a different OS. Well, some people do, but it's still a monumental effort to get up to where Linux is today. It's not like Windows either where you get a lot of really tangible benefits (real command line, your OS is your development environment, etc...). Most of the BeOS advantages are things like "uses multiple CPUs better, has a fancy database filesystem, etc..." Stuff that's nice, but not completely different from what's already available.
In fact this was a major sticking point of the old BeOS. The API was missing a lot of features that apps expect (like BSD style sockets) that make porting a real pain. The old BeOS had gcc too, but getting a non-trivial app to compile and run was no mean feat. Granted, back then Linux had the same problem (these were the days before./configure), but Be had a much worse case of it.
Yes yes, the Be folks loved to play 5 mp3s at the same time just to show off, but when you got down to the brass tacks the system was just different enough (especially with the networking API) to make porting applications a PITA. It took forever to get a web browser (and this was in 1997!) that wasn't a total waste of bits and driver support was considerably worse than Linux or even FreeBSD back then.
I even remember the BeBoxes, with their twin row of LEDs up the front of the case that would should you the load of each (PowerPC) processor. I guess my big problem is that it always felt like a big impressive tech demo instead of an OS. I had a roommate with it and he was always strugging to get non-trivial applications running on the thing.
In some ways BeOS was ahead of its time, particularly with all of the multithreading and filesystem, but in other ways it was just too late to the game (Linux ate its lunch and dinner and was already wooing the girlfriend).
Am I the only one who didn't think Doom 3 was all black and white (so to say?). Sure the area was dark, but there were only a handful of sections that totally required the flashlight to see anything. In most of the others you could generally make out the monsters well enough to shoot them.
I thought it was the government that was in the Oil company's pockets. You'll also have a tough time convincing me that Bill was a better friend (best friend) of the oil companies than George W.
Slashdot Mirror
You're saying the original iPhone was a flop in Europe? Certainly that wouldn't have anything to do with not being officially sold there...
Nope, it's just a better made CD. Regular CDs aren't exactly problematic though, so it'll probably be one of those things where it gets used on expensive music collections to make people think they're buying premium stuff.
Beast with a Billion Backs was marketed as a fairly dirty (for Futurama) DVD. There were references to tentacle porn right in the ads. I'm guessing it had a bit of crossover appeal from the people who are really into that. I imagine they were disappointed at the rather religious tone in the DVD. Benders Game was solidly aimed directly at Futurama's fanbase (nerds) so it didn't have the crossover appeal.
In my opinion (because everybody on the internet has an opinion) all three DVDs have been good, but not great. Beast was the weakest of the three, but even it had good parts.
The problem with swapping disks constantly is that most drive connectors (don't know about SATA specifically) are really only designed to be swapped a few hundred times at most. The mechanical stress of constantly unplugging and replugging the drive could very well lead to stress fractures in the connector, especially since they're often held on with just solder.
Cruise ship markup on top of satellite provider markup? And he streamed an entire game? Last time I checked, BGAN service was on the order of $7/MB, given that cruise ships are going to mark that up a factor of 10 or so, and assuming he transferred a few hundred megs it's probably about what you'd expect.
It may be a misconfiguration, but it's also the default configuration. Most phones try to lock on to the best signal, preferring to use the native carrier mode first, but defaulting to whoever will give you any service at all otherwise. Manual selection mode is an option you have to enable, usually buried well down in the option menus somewhere. Of course if the guy in the article were smarter he would have wondered what that little icon (roaming indicator) on his screen was before he watched a streaming telecast.
Sounds to me like your sin went beyond posting meta-griping that was almost certainly off topic, but also to carefully avoid posting anything constructive to counteract the Karma loss.
Oil rigs don't store mass amounts of oil though, at least not the ones that have been decommissioned like these have.
Frankly the safety issues are a lot trickier. Oil rigs aren't the safest places to be to begin with, and when you neglect the maintenance for years it can't get any better.
Depends on what kind of phone. I could charge my Blackberry Pearl off of the low power mode, but it literally took all night. Installing the driver let it charge in about 15-30 minutes, depending on how far I ran it down. The phone even put up a warning message that the charging current wasn't sufficient if you tried. For something like an iPhone I suspect it would take hours and hours to charge on low power mode.
On the other hand, I have a bluetooth headset that charges from zero to full in about half an hour off of just 100mA, so this clearly depends on the device.
You have a phone with S-Video out? Anyway, if you have a phone with a bunch of obscure ports like that, wouldn't it be better to have a separate connector for the power/data/digital audio from whatever weird ports you also have? Separate headphone jacks are hardly unique.
Because of the way USB is designed. If your device does not get attached to a driver, it is stuck on low power mode, which is not sufficient for charging a phone. When a driver is attached, the driver can ramp the port up into high power mode and charge the phone. Often times if you know what you're doing you can avoid installing the whole "driver suite" and the crappy apps you don't want and instead just copy over a .dll file to let your computer charge the phone. Google is your friend in these cases.
You forgot to mention that it's "not even a mother could love it" ugly.
The design is apparently "gigantic opened up hornets nest", and it looks like finding a level surface to put a chair on might be difficult.
So the first question that comes to my mind when someone says "solar powered cellphone" isn't "does it have a pedometer", but rater "how long does it take to recharge and how long does the battery last". For some reason TFA answered my first question, but not the second.
Right now I tend to recharge my phone at night because I use it during the day. This could be a problem with a solar powered cell phone. If it's power efficient enough that I can leave it on my desk at work (under standard fluorescent lighting) and keep it fully charged then this could be great. If I have to leave it on a windowsill in direct sunlight for half of the day every day, it's far less practical.
1. How practical is this technology? Could you mass produce cheap low power receivers to put in every car/computer/etc...? How complex is the transmit circuitry?
2. How resistant is this to atmospheric and other interference? In theory it should be pretty resistant, but in practice who knows.
Needing multiple antennas to get this done sounds like a rather big limitation to me.
Unless your shared storage solution was absurdly large TbE is still going to be overkill. Even 10GbE is difficult to sustain without half a rack full of machines. 40GbE is still considered overkill for pretty much anything outside of an internet backbone link. TbE is more bandwidth than you can handle.
Changing the hash on peer basis would mess the protocol up pretty badly. It's a lot easier just to turn on the encryption stuff.
For those of you who are wondering, my guess is Cee Pee is Child Porn.
TFA specifially says that it doesn't work on encrypted traffic. In fact the whole thing seems to have some rather bogus qualities to it.
It uses a FPGA, but is stuck at a rather pokey 100Mbps. All it does is compare the encoded hash value in the Bittorrent header against a list of known illegal hashes. Hashes you have to program manually.
I've seen commercial boxes that you can already buy that do a lot more than this and faster. He made a big deal about it not disturbing the network, but that's a standard feature. Unless this thing is dirt cheap or something, I don't really see the application.
We can only hope they fired the morons that took over Team Sonic and are forced to look for some less completely retarded people to take over for them.
Big corporation buys some land to put buildings on. Previous occupant happened to be a paper mill, but who cares? Maybe I'm crazy, but I really don't see what's so newsworthy about this.
It's not so much contempt as it is inertia. We spent the better part of a decade getting all of these various applications working on Linux, and nobody wants to go back to square 1 with a different OS. Well, some people do, but it's still a monumental effort to get up to where Linux is today. It's not like Windows either where you get a lot of really tangible benefits (real command line, your OS is your development environment, etc...). Most of the BeOS advantages are things like "uses multiple CPUs better, has a fancy database filesystem, etc..." Stuff that's nice, but not completely different from what's already available.
In fact this was a major sticking point of the old BeOS. The API was missing a lot of features that apps expect (like BSD style sockets) that make porting a real pain. The old BeOS had gcc too, but getting a non-trivial app to compile and run was no mean feat. Granted, back then Linux had the same problem (these were the days before ./configure), but Be had a much worse case of it.
Yes yes, the Be folks loved to play 5 mp3s at the same time just to show off, but when you got down to the brass tacks the system was just different enough (especially with the networking API) to make porting applications a PITA. It took forever to get a web browser (and this was in 1997!) that wasn't a total waste of bits and driver support was considerably worse than Linux or even FreeBSD back then.
I even remember the BeBoxes, with their twin row of LEDs up the front of the case that would should you the load of each (PowerPC) processor. I guess my big problem is that it always felt like a big impressive tech demo instead of an OS. I had a roommate with it and he was always strugging to get non-trivial applications running on the thing.
In some ways BeOS was ahead of its time, particularly with all of the multithreading and filesystem, but in other ways it was just too late to the game (Linux ate its lunch and dinner and was already wooing the girlfriend).
Am I the only one who didn't think Doom 3 was all black and white (so to say?). Sure the area was dark, but there were only a handful of sections that totally required the flashlight to see anything. In most of the others you could generally make out the monsters well enough to shoot them.
I thought it was the government that was in the Oil company's pockets. You'll also have a tough time convincing me that Bill was a better friend (best friend) of the oil companies than George W.