But it's far more questionable whether he would welcome the iPhone 5C—almost certainly a low-margin device, despite its current-generation components and plastic body—taking a bite out of the more expensive, and presumably higher-margin iPhone 5S

Seriously? This guys thinks the margins on the iPhone 5c are *lower* than the 5s? In that case, why is everybody else complaining about how expensive the 5c is, and saying it should have been released at a $300 price point? If you believe that the 5c could be made & sold at $300 (and I do), then since it sells at $550, Apple *must* be making something like 40% margins on them. The 5s is $100 more, but I bet it's considerably more-expensive to make.

Buy them here

http://www.sakuraofamerica.com/Pen-Archival

These are my favorite sketching / writing pens.
Read all about them here.

It's likely that the percentage of outsourced projects tracks the prevalence of security problems. Certainly, the government has a very high level of outsourced vs in-house development. I think that financial institutions also tend to largely outsource (especially customer-facing) development.

I'd be willing to put a reasonable amount of money at risk predicting that Apple will eventually ship something that's not an iPhone or iPad, which runs the full version of Mac OS X on the ARM architecture. Given how smooth (relatively speaking) the PPC-to-Intel transition went, it'd be a minor speed bump for most developers, not a major disaster. If you're already supporting PPC and Intel, then ARM is just a testing burden - you already need to code for big- and little-endian architectures, for example.

Given the Mac App Store, there's a lot less in the way of friction to just recompile something and put it out there, as opposed to trying to get boxes on retail shelves. Yes, third-party developers will complain, and so will users if they can't get whatever apps they depend on right away. Given that Macs already come with all the basics (email, web, music/video playback), probably 75% of typical users wouldn't even need to buy anything for an ARM Macbook Air to get plenty of use out of it.

If you're willing to include software that was developed, but not released, there are:
    m68k (original NeXT hardware)
    i386 (NEXTSTEP for Intel processors)
    SPARC (NEXTSTEP for SPARC)
    HPPA (NEXTSTEP for PA-RISC)
    Motorola m88k (NeXT RISC Workstation - never released, but a working copy was at Apple when I worked there)
    PowerPC (Mac OS X Server 1.0, later developed into Mac OS X)

Significant bits of NeXT software were also ported to Intel i860 and DEC Alpha, but not enough of the OS to actually qualify as a "NEXTSTEP port"

I'm not sure I'm understanding the question, here. Do you mean could it be included with Android? Absolutely - the license allows that, though I'm not sure what advantage shipping a version of Enyo with an Android distribution would be. It'd likely be out of date fairly rapidly.

If your question was more along the lines of "will Enyo apps run on Android", then the answer is it depends a bit on what version of Android - there are some significant bugs with some Android browsers That said, the intent is for Enyo 2.0 to be compatible with as many web browsers as possible.

Yeah, the "adult is the murderer of the child' metaphor is fairly common in literature, but it's not something people use in everyday conversation, which is what the dialog in a movie supposedly represents. Like I said, even if Obi-wan is just trying to skirt around the truth, it really doesn't reflect well on him, or on the Jedi in general. Yes "your father is a mass-murderer who turned to the dark side of the force and now calls himself Darth Vader" wouldn't be a nice thing to hear, but keeping Luke's parentage a secret from him is leaving him open to be pretty badly blindsided in the future.

Not that it's particularly relevant, but that's simply not correct. Here's what the ghost of Obi-wan has to say about Leia in Episode VI, after Luke figures out that she's his sister:

Anyway, like I said, these are relatively minor nots compared to the problems trying to tie the prequels and the originals together (for example, nearly everything Obi-wan says to Luke in episode IV makes no sense taken in the context of the prequels), but it's pretty clear that the original movie was written as a stand-alone, and the plot twists in later movies were not planned for in the original.

There's a new enyojs.com website, where you can read about Enyo and try out some example apps, as well as downloading the current version.

The most obvious problem is that in Episode IV, Darth Vader killed Luke's Father. In Episode V, it's "revealed" that Darth is Luke's father. It's not "impossible" to reconcile, but Obi-wan saying "what I told you was true, from a certain point of view", is an obvious attempt to wallpaper over this inconsistency. Best case, it just makes Obi-wan look like a liar and untrustworthy.

Another issue comes up when Obi-wan's ghost and Yoda are discussing Luke's running off to save his friends at Cloud City:
Yoda: Told you I did. Reckless is he. Now, matters are worse.
Obi-Wan: That boy is our last hope.
Yoda: No. There is another.

Seriously? Obi-wan doesn't remember that Luke has a twin sister?

Anyway, those are just off the top of my head. Nothing like the horrible plot holes ewhen you try to connect the prequels with the original movies, but not great for movies that were made one after the other, a couple of years apart.

Swapping out Li-Ion batteries isn't like swapping out propane tanks. The value of a propane tank is basically $0, plus the cost of the propane. The cost structure on the batteries is exactly the opposite - the charge is essentially free, but the batteries cost thousands of dollars.

In order for battery-swapping to make sense, the same entity has to own all of the batteries, or there needs to be careful tracking and accounting for wear and tear on each battery. Otherwise, there's an economic incentive to cheat.

Way to move the goalposts, there. Your original statement was that Apple was "not contributing anything back to the community", and that's clearly not the case.

Apropos of this discussion, look at one of the lists and see what sorts of licenses those projects are licensed under. The majority are APSL, which means that they're Apple-developed code which was released to the wider community without any requirement to do so. Of the remaining, about one third are BSD licensed, a third are GPL, and the rest are a variety of other licenses.

Note that the BSD-licensed code doesn't carry any requirement for Apple to release their source code, either. You might wish that Apple would release more of their code under an Open Source license, but that doesn't mean they're benefitting from Open Source without contributing back.

You can make this work if you do what the game console makers have historically done - get commitments from parts suppliers on price reductions over the expected lifetime of the product (due to Moore's law, etc) and aggressively plan as much cost-reduction as possible. You then sell the product for what it *should* cost when the product is mature. You lose a fortune on the first units, but the bleeding stops and eventually you can sell them at a profit.

Of course, if you mis-estimate the lifecycle, or fail to get the expected volumes, this is *really* risky. It's also not really clear what the expected lifetime of a tablet is, yet. The market's just not as mature as the video game console market.