Surely doing that would require them to rewrite the Apache license (thus making it no longer the apache license) otherwise there's no legal way of enforcing the non-commercial use?
One thing to keep in mind though is that you can comfortably read text that is quite a bit smaller on retina, so you can work at a higher application zoom level, which gives you back some space. Not sure whether the interface elements are too big for this display size, but intuitively the resolution sounds about right, it's about the same as the old (beloved) Powerbook 12'' as far as I remember.
You would probably get a better deal selling the watch as a watch itself than melting it down for its raw gold.
Apple has let you bring you old devices in to be recycled in the past however; Maybe they could extend this to buy back old watches? People have envisioned some upgrade program, though I'm doubtful Apple would be too concerned with melting down old watches for their gold.
If the tech is outdated enough that the OS no longer receives updates, then it's value will be similar to that of a first generation iPad.
I'm sure Apple could buy back, clean, and reuse bands from obsolete watches, but they might be the only buyers if iGold is too difficult for a regular jeweler to work with. It will be interesting to see if one of Apple's first moves on entering the jewelry market is to hamstring the independent secondary market.
They still have to sell the watch itself with their margins however. There's nothing stopping you from buying an aftermarket strap, and if they require you to purchase a strap with the watch -- well then it doesn't matter how they split the price up.
There seemed to be plenty of people from lots of different parts of the world. If you were actually concerned about diversity maybe you should be looking more than skin deep yourself.
I've just never encountered that use case in Ruby code, and to me it feels like really bad style. You can use .find to find the first element that matches a block, then return that item (if one exists).
It doesn't look like fantastic Ruby code, you're right. I just wouldn't agree that JS "works well" when it comes to their somewhat afterthought functional iterators.
What doesn't work well? The only thing I can think of, which comes up on occasion, is that you can't manually stop iteration in forEach without ugly tricks like throwing and catching an exception. I actually wanted that behavior for the first time recently, so I just used JQuery's each which lets you stop iteration by returning false. I'm assuming other JS utility libraries like underscore provide something similar.
RE binaries, compilability seems difficult due to how dynamic method calls are, but Rubymotion seems to have solved that to some extent, though it's a shame it requires a subscription to even develop on which doesnt appeal.
What are the "hacky" methods currently used for packaging you mentioned? The only methods I'm aware of no longer work or still require a separate runtime.
