The Tesla P85+ has the same performance 0-60 as the Carrera GT: 3.9s (the speed range where normal humans would use the power), is the safest car you can buy, and costs 1/4 of the Porsche!
Actually the letter from Tesla said that, while the firefighters did follow their own standard procedure and ultimately got it under control, it would have been better in this case if they had not punctured the battery pack to inject water. The letter says these holes allowed the flames to enter the trunk area. The implication is that perhaps the fire would have remained confined to one section of the the (individually fire-walled) battery compartment or directed away from the car had it not been holes punched in the top.
Also, it's really interesting to read some of the patents that Tesla has on the battery technology. They include coating the individual battery cells in an "intumescent" material that expands and insulates the cells if they exceed a certain temperature. So the cells are effectively individually firewalled to try to limit the spread of heat through the compartments and redirect dangerous levels of heat to the metal casing.
Tesla put a lot of thought into this and from everything we know the car behaved exactly as it was designed.
A) I never said it was reasonably priced. I said that for some people the gas savings would make it "more reasonably priced"... i.e. when compared another car that could conceivably be considered in the same class such as a mid-range BMW or Audi. Some people have long commutes and burn hundreds of dollars worth of gas a month... For those people the car is not *that* much of a premium over another other luxury car.
B) The car should have almost no maintenance... No trips to the gas station, no oil changes, no transmission fluid. Brakes pads may not need changing since you hardly ever hit the brakes (regen braking is a better way to drive). How much is that worth?
C) It's by a wide margin the safest car in the world right now... How much is that worth?
D) It's car that can hold seven passengers plus luggage and do 0-60 in 5.x seconds... How much is that worth?
E) It gets over the air software updates that make it better several times a year...
F) It's pretty and fun and a from a little bit in the future...
The Model S starts in the $60k range and for many people who finance and factor in the gas savings monthly the payments are equivalent to that of more reasonably priced car right out the door. Also Tesla has stated that they are planning a more mass market mid-priced car in 2-3 years.
Elon Musk addressed this at the Model X event. Tesla says that if you live in CA and take power from the grid you end up producing 1/4 the CO2 as a gas car and in the worst case scenario where you live in West Virginia and get most electricity from coal you still only produce 1/3 the CO2.
I was thinking exactly the opposite - It seems to me that certain types of creative tasks simply do not lend themselves to lots of iteration and refinement... Writing, for example, tends to get worse the more people mess with it. I'm guessing that movie scripts are the same. Obviously there's room for improvement on most kinds of projects, but I just don't see how you do iteration on writing a story or building a jet engine... at least not iteration in the sense of progressive refinement and adding features as in the agile software sense.
I don't know how LinkedIn's login APIs work, but if they use secure user/pass logins and store authentication tokens on the client side as is good practice then in theory exposing these server side generated hashes wouldn't really compromise the system. The problem is that SHA-1 has been broken:( So in theory someone could reverse these and get plaintext passwords and salts or whatever is in them.
This is one reason you don't send password hashes over the network...
I think you are describing those options incorrectly for his case.
--inplace is the opposite of what he wants. As I understand it --inplace will defeat some of the automatic duplicate range detection and save *space on the server* by not duplicating data during transfer. This does not help with network bandwidth but *hurt*. He probably doesn't care about space on the server, he wants his files mirrored quickly.
--update won't hurt him here, but it's probably not necessary as you seem to be describing it backwards. If he just mods files on his laptop and rsyncs the newer files on the laptop will of course get transferred. The only reason to use --update would be if he modded files on the server at home *and* on the laptop and preferred to keep the ones at home.
We had to wait about three years to get the last doubling from 2TB to 4TB for commercially available internal disks. I seriously doubt we'll get *four* more doublings in the next four years.
I mirror data and test it periodically with rsync using the dry-run (-n) and checksum options (-c) to do a full comparison. I usually have more confidence in a new disk after I've done this a few times.
I actually thought it was a joke when I first saw the headline. This has the be the most unfortunate timing of a product release ever. Long live the Sabre (er, Paypale) Pyramid!
Some of the rides at Disneyland have started taking advantage of this idea by moving the passengers along on a moving beltway (kind of like at the airport) next to the ride... So you board the ride without the ride having to slow down at all... e.g. the Buzz Lightyear ride does this and I recall that it worked pretty well.
Apple obviously already has some kind of deal in place with Google for maps... They've used Google maps since day one. And Google has always charged for high volume use of its other APIs... e.g. geo-tagging. This is a non-story.
I can think of dozens of things that they are dying to use that power for: Pumping 4x the pixels for a high resolution display, doing processing related to speech recognition (even if the matching is done server side), running spotlight indexing on local content as you download it... (e.g. your email and docs from the cloud), playing HD video while doing all of the above, supporting a "mission control" style app switcher with live previews and spaces style switching, supporting airplay in the background while you are using the iPad for something else (maybe even someone else controlling it), games with really good physics simulations (which are dominating the app store and making apple millions):), multi-way video chat compositing, and ten things only Steve Jobs has thought of...
A real engineer can speak to this better, but there is a big difference between the "near field" where you are actually coupling magnetically/capacitatively with the source and radiation which transmits energy over an arbitrary distance. I believe if you are stealing power by putting a big coil next to a power line you are essentially making half of a transformer and directly drawing power through it... whereas if you are at a greater distance all you can do is intercept radiated energy, which is already gone as far as the sender is concerned.
With years of fighting around the ISPs, hosting, and blocking of TPB can someone tell me how it is that the domain name has not just been seized? Haven't other names been grabbed / taken down for more specious reasons?
I understand that taking the domain name would not stop any of this, I am just amazed that they haven't tried...
Does anyone know what was involved in "dumping ROMs"? I would have assumed that the private key was buried in the hardware and not directly accessible via software... From his description it sounds like it was just stored in ROM and software obfuscated. If that was the case it seems odd that it took six years for someone to find it...
Both Java and C/C++ are strongly typed languages, which give a lot of information to the compiler and (in the case of Java) runtime. The question here is how much optimization people can do on a loosely typed language like JavaScript... Apparently they can do quite a bit because JS today is screaming faster than a few years ago.
You would expect that, all things being equal, the languages with a runtime (including JavaScript) should beat out those without because they can do things that you can't do statically. People who religiously believe that Java couldn't beat C/C++ simply failed to understand what is going on... Both languages have about the same amount of info, both have a compiler, but one has a runtime that is also a compiler that can go on analyzing and optimizing as the program runs... Which one wins in the long run? Duh.
So the question then is whether JS having a runtime can allow it to work around the lack of type information in the code. Runtimes can do things like observe the type usage and "optomistic inlining" that in some cases may compensate for the loose types. But there may always be cases where there is a penalty for loose types.
I remember scouring the suppliers to buy these years ago... collecting the "good ones" with more memory, etc.... saving them for various projects that I never got time for:)
20 years ago the idea of being able to build a little computer into random things around the house for $10 in parts was crazy cool... It's still cool, but less so:)
First, let me point out that a 2TB (2000 GB) internal disk is only $79 now... So cost should not be the problem. Next, I agree. You have to keep it "live" and migrating with you and also have at least some offsite backup in case of disaster.
If you work exclusively on a laptop then get a NAS (network attached storage) device with two mirrored disks... Use an "old" disk or combination of smaller ones to form an off-site backup. In 3-5 years when you run out of space on your NAS just roll everything onto a new one and make the old one the new off-site backup...
Pile up the old disks in your parent's basement or someplace unchanging like that:)
Slashdot Mirror
The Tesla P85+ has the same performance 0-60 as the Carrera GT: 3.9s (the speed range where normal humans would use the power), is the safest car you can buy, and costs 1/4 of the Porsche!
If Apple releases a smartwatch it will probably be about as much a watch as the iPhone was "just" a phone...
I've never worn a watch in my life but I can *imagine* a wearable computer that is cool and useful enough that I might consider it... Can't you?
Pat
Actually the letter from Tesla said that, while the firefighters did follow their own standard procedure and ultimately got it under control, it would have been better in this case if they had not punctured the battery pack to inject water. The letter says these holes allowed the flames to enter the trunk area. The implication is that perhaps the fire would have remained confined to one section of the the (individually fire-walled) battery compartment or directed away from the car had it not been holes punched in the top.
Also, it's really interesting to read some of the patents that Tesla has on the battery technology. They include coating the individual battery cells in an "intumescent" material that expands and insulates the cells if they exceed a certain temperature. So the cells are effectively individually firewalled to try to limit the spread of heat through the compartments and redirect dangerous levels of heat to the metal casing.
Tesla put a lot of thought into this and from everything we know the car behaved exactly as it was designed.
What happened in the early 90's that made the price go back up? Is that just noise in the graph? Subsidies dropped?
Ok,
A) I never said it was reasonably priced. I said that for some people the gas savings would make it "more reasonably priced"... i.e. when compared another car that could conceivably be considered in the same class such as a mid-range BMW or Audi. Some people have long commutes and burn hundreds of dollars worth of gas a month... For those people the car is not *that* much of a premium over another other luxury car.
B) The car should have almost no maintenance... No trips to the gas station, no oil changes, no transmission fluid. Brakes pads may not need changing since you hardly ever hit the brakes (regen braking is a better way to drive). How much is that worth?
C) It's by a wide margin the safest car in the world right now... How much is that worth?
D) It's car that can hold seven passengers plus luggage and do 0-60 in 5.x seconds... How much is that worth?
E) It gets over the air software updates that make it better several times a year...
F) It's pretty and fun and a from a little bit in the future...
The Model S starts in the $60k range and for many people who finance and factor in the gas savings monthly the payments are equivalent to that of more reasonably priced car right out the door. Also Tesla has stated that they are planning a more mass market mid-priced car in 2-3 years.
Elon Musk addressed this at the Model X event. Tesla says that if you live in CA and take power from the grid you end up producing 1/4 the CO2 as a gas car and in the worst case scenario where you live in West Virginia and get most electricity from coal you still only produce 1/3 the CO2.
Here is the relevant part of the clip:
https://www.youtube.com/watch?feature=player_detailpage&v=YoNd2eMsPHU#t=334s
Why does this video quality suck so badly?
Why are we listening to two random guys speculating about the future? Who are these guys?
I was thinking exactly the opposite - It seems to me that certain types of creative tasks simply do not lend themselves to lots of iteration and refinement... Writing, for example, tends to get worse the more people mess with it. I'm guessing that movie scripts are the same. Obviously there's room for improvement on most kinds of projects, but I just don't see how you do iteration on writing a story or building a jet engine... at least not iteration in the sense of progressive refinement and adding features as in the agile software sense.
I don't know how LinkedIn's login APIs work, but if they use secure user/pass logins and store authentication tokens on the client side as is good practice then in theory exposing these server side generated hashes wouldn't really compromise the system. The problem is that SHA-1 has been broken :( So in theory someone could reverse these and get plaintext passwords and salts or whatever is in them.
This is one reason you don't send password hashes over the network...
I think you are describing those options incorrectly for his case.
--inplace is the opposite of what he wants. As I understand it --inplace will defeat some of the automatic duplicate range detection and save *space on the server* by not duplicating data during transfer. This does not help with network bandwidth but *hurt*. He probably doesn't care about space on the server, he wants his files mirrored quickly.
--update won't hurt him here, but it's probably not necessary as you seem to be describing it backwards. If he just mods files on his laptop and rsyncs the newer files on the laptop will of course get transferred. The only reason to use --update would be if he modded files on the server at home *and* on the laptop and preferred to keep the ones at home.
Pat
We had to wait about three years to get the last doubling from 2TB to 4TB for commercially available internal disks. I seriously doubt we'll get *four* more doublings in the next four years.
I mirror data and test it periodically with rsync using the dry-run (-n) and checksum options (-c) to do a full comparison. I usually have more confidence in a new disk after I've done this a few times.
I actually thought it was a joke when I first saw the headline. This has the be the most unfortunate timing of a product release ever. Long live the Sabre (er, Paypale) Pyramid!
Some of the rides at Disneyland have started taking advantage of this idea by moving the passengers along on a moving beltway (kind of like at the airport) next to the ride... So you board the ride without the ride having to slow down at all... e.g. the Buzz Lightyear ride does this and I recall that it worked pretty well.
Apple obviously already has some kind of deal in place with Google for maps... They've used Google maps since day one. And Google has always charged for high volume use of its other APIs... e.g. geo-tagging. This is a non-story.
They suck. Let's have an option to hide them or demote them.
I can think of dozens of things that they are dying to use that power for: Pumping 4x the pixels for a high resolution display, doing processing related to speech recognition (even if the matching is done server side), running spotlight indexing on local content as you download it... (e.g. your email and docs from the cloud), playing HD video while doing all of the above, supporting a "mission control" style app switcher with live previews and spaces style switching, supporting airplay in the background while you are using the iPad for something else (maybe even someone else controlling it), games with really good physics simulations (which are dominating the app store and making apple millions) :), multi-way video chat compositing, and ten things only Steve Jobs has thought of...
A real engineer can speak to this better, but there is a big difference between the "near field" where you are actually coupling magnetically/capacitatively with the source and radiation which transmits energy over an arbitrary distance. I believe if you are stealing power by putting a big coil next to a power line you are essentially making half of a transformer and directly drawing power through it... whereas if you are at a greater distance all you can do is intercept radiated energy, which is already gone as far as the sender is concerned.
With years of fighting around the ISPs, hosting, and blocking of TPB can someone tell me how it is that the domain name has not just been seized? Haven't other names been grabbed / taken down for more specious reasons?
I understand that taking the domain name would not stop any of this, I am just amazed that they haven't tried...
Does anyone know what was involved in "dumping ROMs"? I would have assumed that the private key was buried in the hardware and not directly accessible via software... From his description it sounds like it was just stored in ROM and software obfuscated. If that was the case it seems odd that it took six years for someone to find it...
LightPeak is a much cooler name... and less ambiguous as a search term... and less childish sounding.
Both Java and C/C++ are strongly typed languages, which give a lot of information to the compiler and (in the case of Java) runtime. The question here is how much optimization people can do on a loosely typed language like JavaScript... Apparently they can do quite a bit because JS today is screaming faster than a few years ago.
You would expect that, all things being equal, the languages with a runtime (including JavaScript) should beat out those without because they can do things that you can't do statically. People who religiously believe that Java couldn't beat C/C++ simply failed to understand what is going on... Both languages have about the same amount of info, both have a compiler, but one has a runtime that is also a compiler that can go on analyzing and optimizing as the program runs... Which one wins in the long run? Duh.
So the question then is whether JS having a runtime can allow it to work around the lack of type information in the code. Runtimes can do things like observe the type usage and "optomistic inlining" that in some cases may compensate for the loose types. But there may always be cases where there is a penalty for loose types.
I remember scouring the suppliers to buy these years ago... collecting the "good ones" with more memory, etc.... saving them for various projects that I never got time for :)
20 years ago the idea of being able to build a little computer into random things around the house for $10 in parts was crazy cool... It's still cool, but less so :)
First, let me point out that a 2TB (2000 GB) internal disk is only $79 now... So cost should not be the problem. Next, I agree. You have to keep it "live" and migrating with you and also have at least some offsite backup in case of disaster.
If you work exclusively on a laptop then get a NAS (network attached storage) device with two mirrored disks... Use an "old" disk or combination of smaller ones to form an off-site backup. In 3-5 years when you run out of space on your NAS just roll everything onto a new one and make the old one the new off-site backup...
Pile up the old disks in your parent's basement or someplace unchanging like that :)
Pat