There are quite a few worthwhile movies on Netflix. Not looking terribly hard: Eternal Sunshine of the Spotless Mind, Ghostbusters, Dr. Strangelove, Fargo, Big Trouble in Little China, Silence of the Lambs, Airplane, Taxi Driver, The Usual Suspects, Donnie Brasco, The Hunt For Red October, Clue, American Psycho, Pulp Fiction, What's Eating Gilbert Grape, The Truman Show, Who Framed Roger Rabbit?, Terminator 2, Nightmare Before Christmas...
If you're a child of the 80s or early 90s, there is a pretty good collection of nostalgia fare there, too: Ferris Bueller's Day Off, Weird Science, Pretty in Pink, Cry-Baby, Clueless, Footloose, Heathers, Say Anything, Ghost, License to Drive, Planes Trains and Automobile, Airheads, Beavis and Butthead do America, Spaceballs, Robin Hood: Men in Tights, The Adams Family, Adams Family Values, Scrooged, The Naked Gun, Explorers, Dreamscape, The Golden Child, Coming to America...
And of course if you have kids, the deals with Disney and Dreamscape have broadened the selection pretty drastically: The Croods, Mulan, Hercules, Pocahontas, Lilo and Stitch, The Emperor's New Groove, The Aristocats, Robin Hood, The Hunchback of Notre Dame, The Prince of Egypt, Paranorman, Joseph: King of Dreams, Antz, James and the Giant Peach, The Fox and the Hound, Turbo, and all the Dreamworks [Shrek, Madagascar, How to Train Your Dragon, Monsters v Aliens, Kung Fu Panda] holiday specials.
There are definitely relatively few newer releases, but the catalog is significantly improved from when I first signed up.
Yes, narrower at ~ 67" vs 40". But roadways and most parking is built to accommodate cars, which are wider than both. I suppose you could potentially double up along side traditional motorcycles, though.
I'm not sure I see any particular risk to pedestrians. They shouldn't be in traffic in the first place, for starters.
The point was not to contrast specific vehicles, but the basic design. There have been a number of other EV microvehicles produced or designed, including a number of three-wheeled variants like the ZAP Alias, Toyota i-Ride, Aptera 2, and Green Vehicles Tirac.
What specific value is there in using two wheels and a "code heavy" stability algorithm instead of using more vehicles. For example, Elio motors is aiming for 84mpg with a three wheel car that uses "no special technology" and is expected to cost $6800.
Erm, by 1996 we had Linux 1.2, which had loadable kernel modules and a full development toolchain, and Solaris 2, which included "no C compiler, not even a crippled one" *
This was typical of Unix distributions of the era. Development tools for pretty much all the major Unix flavors cost hundreds, if not thousands of dollars. User space tools tended to be relatively primitive compared to their GNU equivilents (e.g. tar often supported only the old v7 or ustar variants which imposed path and file type limitations). Daemons that are not considered standard (sshd, ftpd, httpd) were often expensive and usually third party.
And yes, many commercial Unix variants of the time still required relinking the kernel. OpenServed still required it up until 2005.
The ecosystem is small, but that doesn't mean it doesn't exist. And it may never get appreciably larger. Much like audiophile level equipment and vinyl, high resolution audio is a niche market.
It strikes me as highly unlikely that the Pono music store will do much better than SACD or DVDA did in convincing people they should pay $20-30 for an albums they probably already own and paid $5-15 for, or that the Pono music player will become any more mainstream than existing hi-fi portables, like the HiFiMAN HM-602 or Fiio X3.
If anything, I think the market for dedicated music players will continue to diminish as people increasingly opt for the "good enough" quality of listening to streaming services through general purpose devices.
Oh, don't doubt that there are plenty of repackaged masters out there, though hopefully some are taken from SACD or DVD-A masters instead.:)
I haven't put much energy into a comparison myself, but I haven't seen anything that suggests even a theoretical benefit beyond 24/96, and frankly much benefit beyond 16/44. But I appreciate the push for lossless, at least.
True, but you need at least a double failure to lose data instead of a single failure. More if you keep multiple generations around.
No solution will be perfect, of course. Even a theoretically ideal setup with on-line redundancy, regular snapshots and off-site backups can still fail with a sufficiently ingenious snafu. But that doesn't reduce the utility of relatively simple steps to guard against more mundane errors.
Of course. Performance issues are often a matter of using a more efficient algorithm rather than a more efficient language. But in my experience, Java has the superior ecosystem when it comes to correct and performant packages most of the time.
Depends entirely on what you are storing. A typical blu-ray movie probably runs an average of 25GB or so. You would burn through 20TB in about 800 movies at that rate. Even less if you preserve special features and alternate cuts ( Hardly an unreasonable collection.
Television series can eat us space even faster. Look at something like like Lost, which comes on 36 blu-ray discs. Then add Star Trek: Next Generation (+35), Doctor Who (+29), Battlestar Galactica (+20), Farscape (+20), Stargate: Atlantis (+20), Star Trek (+20), Heroes (+18)... We're up to 198 discs so far. Even at single layer capacity, that is around five terabytes of data with only a handful of shows. Add in Firefly, the later Star Treks, Babylon 5, Lexx, X-Files, Carnivale, Prisoner, Alien Nation, Red Dwarf, Torchwood, Blake's 7, Fringe, Twilight Zone, Outer Limits, Angel, Buffy, Dollhouse, Terminator: The Sarah Conner Chronicles and you could easily most of the space with just sci-fi / fantasy content.
From the "Measuring the Information Society" report report prepared by the United Nations International Telecommunication Union:
"Between 2010 and 2011, mobile-cellular subscriptions uptake of both fixed (wired)-broadband and mobile-registered continuous double-digit growth in developing-country markets, but an overall slowdown in comparison with previous years. The number of mobile-cellular subscriptions increased by more than 600 million, almost all of them in the developing world, to a total of around 6 billion, or 86 per 100 inhabitants, globally".
You realize, of course, that systemd bears many similarities to launchd on MacOS X, which " essentially a replacement for init, rc, init.d script, rc.d script, SystemStarter, inetd / xinetd, crond / atd, [and] watchdogd"?
Processors aren't the bottleneck; I/O bandwidth is. The "weeds of 'structured' crap" is the difference between a log query running in milliseconds or hours when you're generating terabytes of log data every day.
There are quite a few worthwhile movies on Netflix. Not looking terribly hard: Eternal Sunshine of the Spotless Mind, Ghostbusters, Dr. Strangelove, Fargo, Big Trouble in Little China, Silence of the Lambs, Airplane, Taxi Driver, The Usual Suspects, Donnie Brasco, The Hunt For Red October, Clue, American Psycho, Pulp Fiction, What's Eating Gilbert Grape, The Truman Show, Who Framed Roger Rabbit?, Terminator 2, Nightmare Before Christmas...
If you're a child of the 80s or early 90s, there is a pretty good collection of nostalgia fare there, too: Ferris Bueller's Day Off, Weird Science, Pretty in Pink, Cry-Baby, Clueless, Footloose, Heathers, Say Anything, Ghost, License to Drive, Planes Trains and Automobile, Airheads, Beavis and Butthead do America, Spaceballs, Robin Hood: Men in Tights, The Adams Family, Adams Family Values, Scrooged, The Naked Gun, Explorers, Dreamscape, The Golden Child, Coming to America...
And of course if you have kids, the deals with Disney and Dreamscape have broadened the selection pretty drastically: The Croods, Mulan, Hercules, Pocahontas, Lilo and Stitch, The Emperor's New Groove, The Aristocats, Robin Hood, The Hunchback of Notre Dame, The Prince of Egypt, Paranorman, Joseph: King of Dreams, Antz, James and the Giant Peach, The Fox and the Hound, Turbo, and all the Dreamworks [Shrek, Madagascar, How to Train Your Dragon, Monsters v Aliens, Kung Fu Panda] holiday specials.
There are definitely relatively few newer releases, but the catalog is significantly improved from when I first signed up.
Only five states would require helmets for drivers over 18, and Elio is actively lobbying for exemptions for enclosed vehicles.
And at a weight of only eight hundred pounds and only two wheels, the C-1 is likely subject to the same laws.
Yes, narrower at ~ 67" vs 40". But roadways and most parking is built to accommodate cars, which are wider than both. I suppose you could potentially double up along side traditional motorcycles, though.
I'm not sure I see any particular risk to pedestrians. They shouldn't be in traffic in the first place, for starters.
The point was not to contrast specific vehicles, but the basic design. There have been a number of other EV microvehicles produced or designed, including a number of three-wheeled variants like the ZAP Alias, Toyota i-Ride, Aptera 2, and Green Vehicles Tirac.
Er, using more WHEELS.
What specific value is there in using two wheels and a "code heavy" stability algorithm instead of using more vehicles. For example, Elio motors is aiming for 84mpg with a three wheel car that uses "no special technology" and is expected to cost $6800.
Erm, by 1996 we had Linux 1.2, which had loadable kernel modules and a full development toolchain, and Solaris 2, which included "no C compiler, not even a crippled one" *
This was typical of Unix distributions of the era. Development tools for pretty much all the major Unix flavors cost hundreds, if not thousands of dollars. User space tools tended to be relatively primitive compared to their GNU equivilents (e.g. tar often supported only the old v7 or ustar variants which imposed path and file type limitations). Daemons that are not considered standard (sshd, ftpd, httpd) were often expensive and usually third party.
And yes, many commercial Unix variants of the time still required relinking the kernel. OpenServed still required it up until 2005.
* http://www.science.uva.nl/pub/...
The ecosystem is small, but that doesn't mean it doesn't exist. And it may never get appreciably larger. Much like audiophile level equipment and vinyl, high resolution audio is a niche market.
It strikes me as highly unlikely that the Pono music store will do much better than SACD or DVDA did in convincing people they should pay $20-30 for an albums they probably already own and paid $5-15 for, or that the Pono music player will become any more mainstream than existing hi-fi portables, like the HiFiMAN HM-602 or Fiio X3.
If anything, I think the market for dedicated music players will continue to diminish as people increasingly opt for the "good enough" quality of listening to streaming services through general purpose devices.
Oh, don't doubt that there are plenty of repackaged masters out there, though hopefully some are taken from SACD or DVD-A masters instead. :)
I haven't put much energy into a comparison myself, but I haven't seen anything that suggests even a theoretical benefit beyond 24/96, and frankly much benefit beyond 16/44. But I appreciate the push for lossless, at least.
HDtracks, eClassical, Linn, Bandcamp. All carry 24-bit, high resolution audio.
This expands the ecosystem; it doesn't create it.
True, but you need at least a double failure to lose data instead of a single failure. More if you keep multiple generations around.
No solution will be perfect, of course. Even a theoretically ideal setup with on-line redundancy, regular snapshots and off-site backups can still fail with a sufficiently ingenious snafu. But that doesn't reduce the utility of relatively simple steps to guard against more mundane errors.
An SD movie can easily be 6-8GB. An HD movie can easily be 30-50GB.
One word - snapshots.
Are you bad at math, or have you been in a coma long enough that you'r'e unfamiliar with high definition video?
Your definition if "easy to recreate" is different than mine.
(And really, what is the point of buying Blu-Ray if you're going to transcode it to half (or less) the bitrate of a DVD?)
Of course. Performance issues are often a matter of using a more efficient algorithm rather than a more efficient language. But in my experience, Java has the superior ecosystem when it comes to correct and performant packages most of the time.
Depends entirely on what you are storing. A typical blu-ray movie probably runs an average of 25GB or so. You would burn through 20TB in about 800 movies at that rate. Even less if you preserve special features and alternate cuts ( Hardly an unreasonable collection.
Television series can eat us space even faster. Look at something like like Lost, which comes on 36 blu-ray discs. Then add Star Trek: Next Generation (+35), Doctor Who (+29), Battlestar Galactica (+20), Farscape (+20), Stargate: Atlantis (+20), Star Trek (+20), Heroes (+18)... We're up to 198 discs so far. Even at single layer capacity, that is around five terabytes of data with only a handful of shows. Add in Firefly, the later Star Treks, Babylon 5, Lexx, X-Files, Carnivale, Prisoner, Alien Nation, Red Dwarf, Torchwood, Blake's 7, Fringe, Twilight Zone, Outer Limits, Angel, Buffy, Dollhouse, Terminator: The Sarah Conner Chronicles and you could easily most of the space with just sci-fi / fantasy content.
Last time I replaced perl with Java, I got an order of magnitude increase in performance. I'll stick with Java.
A bill introduced by a Democrat and co-sponsored by 13 Democrats (and 0 Republicans) is clearly a Republican initiative.
From the "Measuring the Information Society" report report prepared by the United Nations International Telecommunication Union:
"Between 2010 and 2011, mobile-cellular subscriptions uptake of both fixed (wired)-broadband and mobile-registered continuous double-digit growth in developing-country markets, but an overall slowdown in comparison with previous years. The number of mobile-cellular subscriptions increased by more than 600 million, almost all of them in the developing world, to a total of around 6 billion, or 86 per 100 inhabitants, globally".
You realize, of course, that systemd bears many similarities to launchd on MacOS X, which " essentially a replacement for init, rc, init.d script, rc.d script, SystemStarter, inetd / xinetd, crond / atd, [and] watchdogd"?
Processors aren't the bottleneck; I/O bandwidth is. The "weeds of 'structured' crap" is the difference between a log query running in milliseconds or hours when you're generating terabytes of log data every day.
Dell, who knows what is going on with that.
Leveraged buyout, narrowly averted proxy fight, some shake up of C-level executives, and a workforce reduction of a few thousand.
You're welcome.
You might point out that the Video Player Tutorial on the VIERA Connect Developer portal uses jQuery.
RDP has supported remote applications since 2007: http://msdn.microsoft.com/en-u...