They're not that far off now. Your goal is 20 minutes for 200 miles of range, Tesla is doing ~110 miles in that amount of time. They've said that they might eke a little bit more out of it the current cars and chargers (they do 120 kW today, and are planning to move to 135), which would get them up to ~130 miles per 20 minutes), but that future bumps will require improvements to the hardware itself.
Superconducting cabling is feasible (although I doubt they have a great bend radius), but that only solves one segment of the wiring problem. You still need to move the energy around in the car, and in the charge station.
Also, I wouldn't want to be around if somebody accidentally cuts a superconducting charge cable. Liquid nitrogen spraying everywhere is bad.
And my.com/.net/.org domain (that costs less than $25/year) gets me an infinite number of changeable names. I simply set the TTL on the subdomains low and update it whenever the IPs change.
It also means that, in marginal conditions, it can reconstruct code blocks that it didn't manage to read correctly. It's not just useful for printed codes.
Where does what say that? The center console is used to control braking behaviour, suspension height, and all sorts of other driving parameters. And they do firmware updates of the whole set.
QR codes use Reed-Solomon error correction, so you don't get missing or corrupt data (in that the QR reader knows if it reconstructed all the data correctly or not). Readers will typically only "read" the code if they manage to reconstruct the entire thing. The error correction helps compensate for poor image quality, and the fact that the image is monochrome makes things like exposure less critical. There are four levels of error correction, which allow for the reconstruction of 7%, 15%,25%, or 30% of codewords respectively.
QR codes can store up to a bit under 3KB of data (the largest size with the lowest error correction), but I couldn't get my phone to read any v40 QR codes (the largest ones), and v25 took some effort. The plan for QR codes of kernel oopses will probably fail for that reason, if nothing else (that they need v40 codes to store an entire oops, and few phones will read v40 codes).
As others have pointed out, there's a hell of a lot more connectivity between the two systems than you're implying, and... firmware updates would be done over the same network that jailbreakers are messing with.
If you want to jailbreak your phone/tablet/television/refrigerator/etc., power to you. If you do anything that impairs reliability, the worst case is that you can't make a phone call, or your ice-cream melts. You're not having any impact on other people.
If you jailbreak your car, however, and inadvertently change something that impairs reliability, you're compromising the safety of everybody else on the road. Everything (including braking) in Tesla cars is tied into the software, and this is not something you should mess around with.
Price? It's priced competitively with other cars in its class (most people don't buy luxury sedans).
Cross-country trip? What about it? The supercharger network reaches coast to coast, and by the end of the year there will be a few more cross-country routes possible.
LA to SF? This was literally the first place they built superchargers.
Why do they insist on putting a post inside the socket? They end up making both the socket and the connector more delicate. Instead of the connector being one solid piece and the socket being just an empty socket, it means the connector has to be hollow, and more prone to damage. The correct solution here was not to just make micro B symmetrical and cram more pins on it...
All you had to do was make something similar to Apple's lightning connector, not to compound the existing problems.
A company branching out into tangentially related fields? It's like when that fruit-themed computer company decided to get into the record business. That sure didn't go anywhere, did it? Or when they decided they were going to try their hand at making telephones, what a lark!
I'm not a fan of Facebook, but I think this is a good partnership for both parties, as well as consumers.
Most game developers use Steam (which takes a similar 30% chunk of sales revenue, like Apple), even though there is nothing stopping developers from doing it themselves on that platform.
The American sequestration didn't help ZFSonLinux, since the primary developer is Lawrence Livermore National Laboratory (a research lab funded by the US government). But the pace of development has been pretty constant:
How much of a game sale do you think game developers get from a retail box on a shelf, after they've covered the cost of paying the publisher, the manufacturer, the shipper, the store, and any other middle men I'm forgetting? A damned sight less than the 70% that Apple gives you on their app store. Or Valve gives you on Steam.
30% for digital distribution seems to be relatively standard.
First is the obvious thing to note, Sony's solution is PS4-only, while the Rift will (at least initially) be PC-only. So they're not directly competing in that respect. But more importantly is that for developers, Sony's solution and Oculus' solution pose all the same problems. You need to figure out input, locomotion, figure out the rules of VR (what feels good and what doesn't), figure out what sort of gameplay works best...
The more developers there are working on VR content, the better the entire VR ecosystem gets. The biggest risk to Oculus in my mind has always been that they'd have trouble getting enough compelling content. Sony's involvement will help with that.
The DS/3DS treat the two separate screens more like one larger screen. Heck, in the 2DS, they literally are one LCD panel with a bezel stuck on top in the middle. There's a big difference between looking up and down on a tall screen versus shifting your focus from a screen 10 feet away and a screen a foot or two away.
They said their reasoning was that a screen on the controller forced you to split your attention between the TV screen and the controller screen. The screen on the controller would only end up being useful when you weren't playing a game, and the cost wasn't worth it for being used strictly for non-gaming.
The only thing that makes ICANN relevant is that they control the root zone that everybody uses. These days, if a few of the larger tech companies (Microsoft/Google/Mozilla/Apple) got together and decided to start their own DNS root zone, ICANN would become irrelevant rather quickly (since those companies control the browsers and mail clients everybody uses, and can do their own DNS lookups).
I'm not saying that would be a good thing, just that I find it interesting that ICANN is seen as being "in charge" as if they have regulatory authority when in reality they only have a say because people use their root zone by convention.
Slashdot Mirror
They're not that far off now. Your goal is 20 minutes for 200 miles of range, Tesla is doing ~110 miles in that amount of time. They've said that they might eke a little bit more out of it the current cars and chargers (they do 120 kW today, and are planning to move to 135), which would get them up to ~130 miles per 20 minutes), but that future bumps will require improvements to the hardware itself.
Superconducting cabling is feasible (although I doubt they have a great bend radius), but that only solves one segment of the wiring problem. You still need to move the energy around in the car, and in the charge station.
Also, I wouldn't want to be around if somebody accidentally cuts a superconducting charge cable. Liquid nitrogen spraying everywhere is bad.
And my .com/.net/.org domain (that costs less than $25/year) gets me an infinite number of changeable names. I simply set the TTL on the subdomains low and update it whenever the IPs change.
It also means that, in marginal conditions, it can reconstruct code blocks that it didn't manage to read correctly. It's not just useful for printed codes.
Where does what say that? The center console is used to control braking behaviour, suspension height, and all sorts of other driving parameters. And they do firmware updates of the whole set.
Except L implies the lowest amount of error correction, making it the hardest to read, and few devices will read 40 codes anyhow. They're enormous.
QR codes use Reed-Solomon error correction, so you don't get missing or corrupt data (in that the QR reader knows if it reconstructed all the data correctly or not). Readers will typically only "read" the code if they manage to reconstruct the entire thing. The error correction helps compensate for poor image quality, and the fact that the image is monochrome makes things like exposure less critical. There are four levels of error correction, which allow for the reconstruction of 7%, 15%,25%, or 30% of codewords respectively.
QR codes can store up to a bit under 3KB of data (the largest size with the lowest error correction), but I couldn't get my phone to read any v40 QR codes (the largest ones), and v25 took some effort. The plan for QR codes of kernel oopses will probably fail for that reason, if nothing else (that they need v40 codes to store an entire oops, and few phones will read v40 codes).
They're encoding the kernel oops. Here's one example oops they're using in that thread:
http://levex.fedorapeople.org/...
And yet it controls braking/acceleration/suspension behaviour, and initiates firmware updates to the whole network.
Car stereos don't control braking.
As others have pointed out, there's a hell of a lot more connectivity between the two systems than you're implying, and... firmware updates would be done over the same network that jailbreakers are messing with.
If you want to jailbreak your phone/tablet/television/refrigerator/etc., power to you. If you do anything that impairs reliability, the worst case is that you can't make a phone call, or your ice-cream melts. You're not having any impact on other people.
If you jailbreak your car, however, and inadvertently change something that impairs reliability, you're compromising the safety of everybody else on the road. Everything (including braking) in Tesla cars is tied into the software, and this is not something you should mess around with.
Price? It's priced competitively with other cars in its class (most people don't buy luxury sedans).
Cross-country trip? What about it? The supercharger network reaches coast to coast, and by the end of the year there will be a few more cross-country routes possible.
LA to SF? This was literally the first place they built superchargers.
Why do they insist on putting a post inside the socket? They end up making both the socket and the connector more delicate. Instead of the connector being one solid piece and the socket being just an empty socket, it means the connector has to be hollow, and more prone to damage. The correct solution here was not to just make micro B symmetrical and cram more pins on it...
All you had to do was make something similar to Apple's lightning connector, not to compound the existing problems.
Maybe because they RTFA'd, and noted the drawings of camera lenses attaching to smartphone cameras in the patent?
Many places get their power from clean sources, like nuclear, or in my case, hydro...
A company branching out into tangentially related fields? It's like when that fruit-themed computer company decided to get into the record business. That sure didn't go anywhere, did it? Or when they decided they were going to try their hand at making telephones, what a lark!
I'm not a fan of Facebook, but I think this is a good partnership for both parties, as well as consumers.
Most game developers use Steam (which takes a similar 30% chunk of sales revenue, like Apple), even though there is nothing stopping developers from doing it themselves on that platform.
The American sequestration didn't help ZFSonLinux, since the primary developer is Lawrence Livermore National Laboratory (a research lab funded by the US government). But the pace of development has been pretty constant:
https://github.com/zfsonlinux/...
Just because the last stable build was released in 2013 doesn't mean there hasn't been work done.
How much of a game sale do you think game developers get from a retail box on a shelf, after they've covered the cost of paying the publisher, the manufacturer, the shipper, the store, and any other middle men I'm forgetting? A damned sight less than the 70% that Apple gives you on their app store. Or Valve gives you on Steam.
30% for digital distribution seems to be relatively standard.
First is the obvious thing to note, Sony's solution is PS4-only, while the Rift will (at least initially) be PC-only. So they're not directly competing in that respect. But more importantly is that for developers, Sony's solution and Oculus' solution pose all the same problems. You need to figure out input, locomotion, figure out the rules of VR (what feels good and what doesn't), figure out what sort of gameplay works best...
The more developers there are working on VR content, the better the entire VR ecosystem gets. The biggest risk to Oculus in my mind has always been that they'd have trouble getting enough compelling content. Sony's involvement will help with that.
Well, ghost mode would now be gone since the touchscreen is gone too.
The DS/3DS treat the two separate screens more like one larger screen. Heck, in the 2DS, they literally are one LCD panel with a bezel stuck on top in the middle. There's a big difference between looking up and down on a tall screen versus shifting your focus from a screen 10 feet away and a screen a foot or two away.
They said their reasoning was that a screen on the controller forced you to split your attention between the TV screen and the controller screen. The screen on the controller would only end up being useful when you weren't playing a game, and the cost wasn't worth it for being used strictly for non-gaming.
So basically cost wasn't the major factor.
The only thing that makes ICANN relevant is that they control the root zone that everybody uses. These days, if a few of the larger tech companies (Microsoft/Google/Mozilla/Apple) got together and decided to start their own DNS root zone, ICANN would become irrelevant rather quickly (since those companies control the browsers and mail clients everybody uses, and can do their own DNS lookups).
I'm not saying that would be a good thing, just that I find it interesting that ICANN is seen as being "in charge" as if they have regulatory authority when in reality they only have a say because people use their root zone by convention.