The OS/2 effect is going strong. It worked so well for IBM, so Blackberry chose to adopt that strategy.
You can't trust IDC data.
Also, treating Android as a single thing is a mistake. You really have to separate out Google Play Android versus Android Open Source Project. They aren't the same thing in terms of how the market behaves, pricing, and the consumer experience.
Many make the wrong assumption that 64 bit processor means only increasing the memory pointers to 64 bit. This is not the case with the transition from the A6 to the A7. The instruction set changed from ARMv7s to ARMv8 (or ARM64). There are performance gains to be made moving to a new, revised ISA for which 64 bit is but one of the characteristics. Further, Apple has been working on their toolchain and they can leverage certain software compiler improvements especially within the Objective C runtime, like tagged pointers and inline reference counting that are made possible with 64 bit pointers.
Absolutely, to be a top notch software developer, learning to code trumps a CS degree. After all, you can get a degree but who knows how much attention you really paid in class. Further, learning to code goes beyond what is taught in a CS degree.
However, this isn't an issue of theory vs. practice. It's like saying, would you rather have a surgeon that learned surgery the traditional route with 4 year degree heavy in science, specifically biology classes and then went to med school, etc, or a self taught surgeon that learned at a field hospital during a war? Obviously, both would have to learn the basics of surgery itself, that is the actual cutting, the sewing, etc. The former is likely to have a far better grounding in a wider range of subjects to treat the patient, even if the a particular of the latter might be better at the actual cutting and sewing.
When one graduates with a CS degree, they might not have yet learned how to code, especially in a professional setting in a group. A coder can learn everything that a person with a CS degree learned, but that is basically going to each of the CS classes. Sometimes the hinderance to getting the degree isn't the CS classes, it's the other classes required for an undergraduate degree. In either case, to be a very good coder, you basically have to master both the theory and the practice.
Lithium is probably under 4% of the total mass of the battery. Tesla's battery is primarily composed of lithium, nickel, aluminum, cobalt, and graphite. Nickel and aluminum are the big constituents by mass of the battery. Total lithium mass per battery is probably around 20kg. For 1,000,000 cars, that's about 22,000 tons. That might be enough to start production in the U.S., but more likely, Canada will supply most of the initial amounts of raw materials including the nickel and lithium.
This "hack" sounds like they brute forced a weak password on the service that that provides access to the Model S mobile apps. That password is shared with the "My Tesla" owner's website. It is possible to set that password to a far longer and complex password, certainly far longer than 6 characters. I suspect this contest was rigged and someone set the password to "111111" or something like that.
The car itself talks to Tesla using an OpenVPN session over 3G or Wifi.
This reasoning, on the face of it, is absolutely ridiculous.
Because one side is very advanced militarily and the other side is not, then the side that is very advanced needs to let the other side have a fairer fight? No. Not at all.
A mugger comes at you with a knife. If you have a gun, that's not fair, you need to let the mugger with the knife stab you a few times before you pull the trigger?
Or let's say the other side has a stone, and is perfectly happy to hit you over the head repeatedly with it until you are dead. You have a M240 light machine gun. Very asymmetrical. You can take out the guy with the stone and a few of his buddies with a burst. But no! Unfair! They should be given machine guns too to make this fair. You should wait until they are given machine guns. Matter of fact, you can watch them get machine guns. So you wait to make sure they get all set up with their new donated machine guns, make sure they get the right training so that they know how to kill you with it, since it is only fair, right? No. If this were you, you would kill them if they are trying to kill you, no matter what weapons they possess, no matter how asymmetrical the military technology.
We are in very twisted times, as Hamas knows it can't really hurt Israel militarily with these tactics, but is very willing to provoke the situation such that they get pummeled. Each time Hamas provokes a pummeling, they get more funding and better weaponry from outside sources and more sympathy from both within and around the world. In the short term, Hamas has no hope of winning militarily. However, they hope that in the long term, they can grow strong enough to take on Israel militarily and wipe them out.
All of this is boiling over to what exactly is considered "YOUR" information in the digital age? Nobody seems to be asking this question.
As a minimum if you don't encrypt it before tossing it out onto unknown public and private networks you don't control, you've already said you don't care who sees / reads / hears / metabolizes your data.
The value of something isn't tied to it's ease of duplication, at all. Property is not the only lens by which to view value. For example, property rights are not in play if I hire someone to clean my garage.
I don't know if you can. In the real world, duplicating objects is impossible. However, duplicating information in computers is essentially free. Therefore, I'm not sure that simulating the notion of "property rights" on a computer even makes sense. It certainly doesn't make sense if it costs DRM to achieve it.
The means by which they revoke permissions after the time limit must be transparent. DRM fails to meet this criteria.
Building a business model around time limits requires you to take rights away from the consumer. You can't justify online video "rentals" if they cannot be built transparently.
At the cell level, Tesla is probably already paying under $250/kWh. Maybe even just under $200/kWh. That's below most lithium iron phosphate battery costs which are already competitive with lead acid batteries for total life cycle costs in an off-grid solar battery setup. So this "too expensive" comment is probably not right. Further, if they recycle battery cells from transportation use to grid storage use, then the costs could be far lower.
I'd say the killer feature is pure remote management. You don't need to physically manage your systems anymore.