Having just watched Revenge of the Electric Car recently, they came very close, to the point where they almost couldn't make payroll, and were only saved by Musk handing over the last of his money, which was basically completely gone because he had already dumped it all into Tesla and SpaceX. If the documentaries depictions of events (and the things Musk says in the documentary) are to be believed, the company came within inches of blowing up, and they did have layoffs. These days, they're in far more favourable shape (in terms of resiliency) than they were back then.
That would work, but it now requires me to have a specific USB drive on me when I need to get a file. That's not always guaranteed in the "Oh, let me just log onto my file storage account on your computer and I'll grab that file for you" situation.
Because unless you're going to memorize your private key so that you can enter it every time you log into the web interface on some computer, you'd have no way to decrypt the data. I presume that you have to move a private key file between any computer you want to use Wuala on? Because if the company is storing both your private and public key on their server, then the client versus server side encryption is moot and it's no better than dropbox (because the company can decrypt your files in either case).
And how would I then upload or download files via the web interface (assuming that there is one)? Client-side encryption would break a lot of Dropbox's advantages.
They switched to 64-bit PowerPC chips, and then promptly migrated to the Intel Core Solo and Core Duo chips, which are 32-bit chips derived from the Pentium M. They could have avoided this extra transition by using AMD's 64-bit chips for their initial transition, but AMD didn't have any decent mobile chips at the time.
The iPad 1 and iPhone 4 are definitely not the same target; one has double the RAM of the other, for one thing, despite both using the A4. That can be a rather important difference for something like a game; you're expected to render the game at a higher resolution, but you've got half the RAM to do it in. And furthermore, within those targets that you've mentioned, the clockspeed varies from 600 MHz on the 3GS to 1GHz on the iPad; that can make a rather big different if your app or game is processor-intensive.
The iPhone 4S and iPad 2 are admittedly much closer together; they only differ (apart from resolution) in clockspeed, and then only by 200MHz. But that ignores the fact that designing an interface or input paradigm for the iPhone/iTouch and the iPad is going to require a different approach, or that you're going to have to account for differences in hardware support (the iPod Touch 4th gen might seem a lot like an iPhone, but it has no GPS/GLOSNASS or compass support, rendering any location-based app nearly useless). The iPad has a compass, but only gets GPS on the 3G models, and no GLASNASS in any version.
It's not even true anymore anyhow. There are so many different classes of Apple hardware that a developer has to target that it's not a homogenous platform anymore. You've got three different resolutions ranging from 480x320 to 1024x768 (not even the same aspect ratio), two incompatible instruction sets (ARMv6 and ARMv7), two incompatible and fundamentally opposite graphics APIs (OpenGL ES 1.x and 2.x, which is kind of like DX7 fixed function versus DX9 programmable), varying amounts of CPU cores, clockspeeds, amounts of RAM, screen sizes... Third-party iOS apps are running on three different device families, and that's only going to broaden when Apple's iTV product comes out.
All told, there are currently twelve different product lines running iOS (with further variations within a product line, such as amount of flash), all with different capabilities, all with different OS version support. For each of those twelve devices, you have to support at least two major OS versions, and potentially a few sub-versions. The feature grid on the wikipedia article (http://en.wikipedia.org/wiki/List_of_iOS_devices) should underscore how non-homogeneous the platform is.
I was running OpenSolaris on the box before, and I haven't particularly noted any speed differences locally. I'm not sure I'm getting as much out of Samba, though.
ZFS now runs pretty well on Linux too, as a kernel module, thanks to zfsonlinux. If you're running a Debian-based distro, installing it is trivial (one command to add the PPA, one command to install the package).
The price tag is directly comparable, because ARM doesn't make processors, they sell licenses to designs. The only relevant metric is really performance at a given power point.
The closest competitor is Intel's Atom chips. At comparable power points, the current ARM chips seem to substantially outperform Atom chips, and the ARM chips scale far lower than Intel's do. It becomes a bit murkier at higher power levels, since until recently nobody was really making ARM chips that high, but we'll see a lot more competition in this field in the future with the ARM Cortex A15, which is intended to be a lot more scalable. The current design is planned to go from 1.0GHz single-core, up to 2.5GHz eight-core, depending on what the integrator wants. On top of that, they've got the new Cortex A7 that they've designed as an ultra-lower performance chip, which is intended to be a much simpler architecture that's still ISA-compatible with the A15. The intention is actually to put an A7 and A15 in the same SoC, so that the SoC can entirely turn off the A15 cores when only low performance is needed (like playing audio or video, since that's done almost entirely on a DSP). This is similar to what nVidia did with the Tegra 3, just taken even farther.
Pray tell me, what kind of aircraft is in th existing arsenal, capable of delivering this turd-of-death?
The B-2 is the intended deployment platform. Each aircraft will be able to carry two of them. They also did their testing with the B-52, introduced in 1955.
I get the whole illegal-no-prescription-drug-ads-are-bad thing, but I've never really understood the American obsession with trying to stop pharmacies from exporting to the US. I guess the price controls that the government puts on drugs wouldn't jive with free trade agreements or something, but since they're not sold below cost, there's nothing preventing US companies from lowering prices to compete.
It's pretty, but it's not a photograph of the earth. It's CG; a rendering of a sphere texturemapped with images of the surface of the planet that they captured. Neither NASA nor huffpost are misrepresenting what it is, but there's something special about the original blue marble, which is an actual *photograph* of the entire planet, not something thrown together in 3ds max.
RTFA. Bell has made an official filing with the CRTC stating their intention to cease all throttling on March 1st, so any such hearing would be pointless. On top of that, Bell's throttling hardware doesn't work the same way, it uses DPI, which at least tries to identify P2P instead of just throttling anything on P2P ports like Rogers does.
The problem the CRTC has is not that Rogers is throttling P2P. That's perfectly allowed under the CRTC's ITMP framework. The problem is that Rogers is throttling anything on P2P ports over a certain speed, and only whitelisting games after the fact. That's not allowed. If I design a new time-sensitive app and run it on the same port as some P2P software, Rogers will throttle it, and then whitelist it if I complain. This is forbidden.
They basically work on a whitelist system now (throttle everything by default and whitelist exceptions), and they need to move to a blacklist (throttle nothing by default and blacklist P2P apps) system to come into compliance with the ITMP framework.
It depends how you define "Canadian" content. Almost anything from SyFy, past and present, is made in Canada. Stargate, Battlestar Galactica, etc. A few network shows are too. Fringe, for example, is shot in Vancouver.
The question becomes, when is a show Canadian? Stargate was shot in Vancouver, with a Canadian crew, a mostly Canadian cast, Canadian writers, Canadian producers... The only thing distinctly American about the show was where the money came from. Does that make Stargate Canadian? Most people seem to think it does, and it tended to win the Spacey award for best Canadian show every year.
Slashdot Mirror
Having just watched Revenge of the Electric Car recently, they came very close, to the point where they almost couldn't make payroll, and were only saved by Musk handing over the last of his money, which was basically completely gone because he had already dumped it all into Tesla and SpaceX. If the documentaries depictions of events (and the things Musk says in the documentary) are to be believed, the company came within inches of blowing up, and they did have layoffs. These days, they're in far more favourable shape (in terms of resiliency) than they were back then.
Right, but an ATM card fits in my wallet. A USB stick doesn't, although something like one of those SD cards with the built in USB headers might.
That would work, but it now requires me to have a specific USB drive on me when I need to get a file. That's not always guaranteed in the "Oh, let me just log onto my file storage account on your computer and I'll grab that file for you" situation.
Because unless you're going to memorize your private key so that you can enter it every time you log into the web interface on some computer, you'd have no way to decrypt the data. I presume that you have to move a private key file between any computer you want to use Wuala on? Because if the company is storing both your private and public key on their server, then the client versus server side encryption is moot and it's no better than dropbox (because the company can decrypt your files in either case).
I see a java app, not a web interface.
And how would I then upload or download files via the web interface (assuming that there is one)? Client-side encryption would break a lot of Dropbox's advantages.
They switched to 64-bit PowerPC chips, and then promptly migrated to the Intel Core Solo and Core Duo chips, which are 32-bit chips derived from the Pentium M. They could have avoided this extra transition by using AMD's 64-bit chips for their initial transition, but AMD didn't have any decent mobile chips at the time.
Wow, and I spelled GLONASS two different ways, both wrong.
The iPad 1 and iPhone 4 are definitely not the same target; one has double the RAM of the other, for one thing, despite both using the A4. That can be a rather important difference for something like a game; you're expected to render the game at a higher resolution, but you've got half the RAM to do it in. And furthermore, within those targets that you've mentioned, the clockspeed varies from 600 MHz on the 3GS to 1GHz on the iPad; that can make a rather big different if your app or game is processor-intensive.
The iPhone 4S and iPad 2 are admittedly much closer together; they only differ (apart from resolution) in clockspeed, and then only by 200MHz. But that ignores the fact that designing an interface or input paradigm for the iPhone/iTouch and the iPad is going to require a different approach, or that you're going to have to account for differences in hardware support (the iPod Touch 4th gen might seem a lot like an iPhone, but it has no GPS/GLOSNASS or compass support, rendering any location-based app nearly useless). The iPad has a compass, but only gets GPS on the 3G models, and no GLASNASS in any version.
It's not even true anymore anyhow. There are so many different classes of Apple hardware that a developer has to target that it's not a homogenous platform anymore. You've got three different resolutions ranging from 480x320 to 1024x768 (not even the same aspect ratio), two incompatible instruction sets (ARMv6 and ARMv7), two incompatible and fundamentally opposite graphics APIs (OpenGL ES 1.x and 2.x, which is kind of like DX7 fixed function versus DX9 programmable), varying amounts of CPU cores, clockspeeds, amounts of RAM, screen sizes... Third-party iOS apps are running on three different device families, and that's only going to broaden when Apple's iTV product comes out.
All told, there are currently twelve different product lines running iOS (with further variations within a product line, such as amount of flash), all with different capabilities, all with different OS version support. For each of those twelve devices, you have to support at least two major OS versions, and potentially a few sub-versions. The feature grid on the wikipedia article (http://en.wikipedia.org/wiki/List_of_iOS_devices) should underscore how non-homogeneous the platform is.
I was running OpenSolaris on the box before, and I haven't particularly noted any speed differences locally. I'm not sure I'm getting as much out of Samba, though.
Isn't that the point of using a filesystem that can do online scrubs, like ZFS? As far as I know, ZFS also checks metadata when scrubbing.
ZFS now runs pretty well on Linux too, as a kernel module, thanks to zfsonlinux. If you're running a Debian-based distro, installing it is trivial (one command to add the PPA, one command to install the package).
That was supposed to be "the price tag ISN'T directly comparable"
The price tag is directly comparable, because ARM doesn't make processors, they sell licenses to designs. The only relevant metric is really performance at a given power point.
The closest competitor is Intel's Atom chips. At comparable power points, the current ARM chips seem to substantially outperform Atom chips, and the ARM chips scale far lower than Intel's do. It becomes a bit murkier at higher power levels, since until recently nobody was really making ARM chips that high, but we'll see a lot more competition in this field in the future with the ARM Cortex A15, which is intended to be a lot more scalable. The current design is planned to go from 1.0GHz single-core, up to 2.5GHz eight-core, depending on what the integrator wants. On top of that, they've got the new Cortex A7 that they've designed as an ultra-lower performance chip, which is intended to be a much simpler architecture that's still ISA-compatible with the A15. The intention is actually to put an A7 and A15 in the same SoC, so that the SoC can entirely turn off the A15 cores when only low performance is needed (like playing audio or video, since that's done almost entirely on a DSP). This is similar to what nVidia did with the Tegra 3, just taken even farther.
Pray tell me, what kind of aircraft is in th existing arsenal, capable of delivering this turd-of-death?
The B-2 is the intended deployment platform. Each aircraft will be able to carry two of them. They also did their testing with the B-52, introduced in 1955.
I get the whole illegal-no-prescription-drug-ads-are-bad thing, but I've never really understood the American obsession with trying to stop pharmacies from exporting to the US. I guess the price controls that the government puts on drugs wouldn't jive with free trade agreements or something, but since they're not sold below cost, there's nothing preventing US companies from lowering prices to compete.
It's pretty, but it's not a photograph of the earth. It's CG; a rendering of a sphere texturemapped with images of the surface of the planet that they captured. Neither NASA nor huffpost are misrepresenting what it is, but there's something special about the original blue marble, which is an actual *photograph* of the entire planet, not something thrown together in 3ds max.
And that's why the CRTC is taking them to task.
Rogers does't even make a distinction between P2P and *ANYTHING* else. That's why they're in trouble.
RTFA. Bell has made an official filing with the CRTC stating their intention to cease all throttling on March 1st, so any such hearing would be pointless. On top of that, Bell's throttling hardware doesn't work the same way, it uses DPI, which at least tries to identify P2P instead of just throttling anything on P2P ports like Rogers does.
If your P2P application is time dependent, it can't be throttled under the CRTC's ITMP framework. If it's not time dependent, it can be.
The problem the CRTC has is not that Rogers is throttling P2P. That's perfectly allowed under the CRTC's ITMP framework. The problem is that Rogers is throttling anything on P2P ports over a certain speed, and only whitelisting games after the fact. That's not allowed. If I design a new time-sensitive app and run it on the same port as some P2P software, Rogers will throttle it, and then whitelist it if I complain. This is forbidden.
They basically work on a whitelist system now (throttle everything by default and whitelist exceptions), and they need to move to a blacklist (throttle nothing by default and blacklist P2P apps) system to come into compliance with the ITMP framework.
It depends how you define "Canadian" content. Almost anything from SyFy, past and present, is made in Canada. Stargate, Battlestar Galactica, etc. A few network shows are too. Fringe, for example, is shot in Vancouver.
The question becomes, when is a show Canadian? Stargate was shot in Vancouver, with a Canadian crew, a mostly Canadian cast, Canadian writers, Canadian producers... The only thing distinctly American about the show was where the money came from. Does that make Stargate Canadian? Most people seem to think it does, and it tended to win the Spacey award for best Canadian show every year.
From a Montreal perspective, smoked meat, bagels, tourtiere, habitant pea soup, maple baked beans, etc.