...is that our selfies are safer.
I keep thinking that if an ISP really wanted to cut costs, they could proactively monitor their network for problems:
- Provide the CPE preconfigured, at no additional cost to the customer. (Build the hardware cost into the price of service.)
- Ensure that the CPE keeps a persistent capacitor-backed log across reboots. If the reboot was caused by anything other than the customer yanking the cord out of the wall or a power outage, send that failure info upstream. Upon multiple failures in less than a few weeks, assume that the customer's CPE is failing, and call the customer with a robocall to tell them that you're mailing them new CPE to improve the quality of their service.
- Detect frequent disconnects and reconnects, monitor the line for high error rates, etc. and when you see this happening, treat it the same way you treat a CPE failure.
- If the new hardware behaves the same way, silently schedule a truck roll to fix the lines.
If done correctly (and if clearly advertised by the ISP so that users would know that they didn't need to call to report any outages), it would eliminate the need for all customer service except for billing, and a decent online billing system could significantly reduce the need for that as well.
They won't see people switching to Swift uniformly. There are trillions of lines of code written in Objective-C, and programmers already know it and are comfortable with it. There are no tools for migrating code from Objective-C to Swift, much less the hodgepodge of mixed C, Objective-C, and sometimes C++ that quite frequently occurs in real-world apps, so for the foreseeable future, you'd end up just adding Swift to your existing apps, which means you now have three or four languages mixed in one app instead of two or three, and now one of them looks completely different than the others. I just don't see very many developers seriously considering adopting Swift without a robust translator tool in place.
I do, however, expect to see Swift become the language of choice for new programmers who are coming from scripting languages like Python and Ruby, because it is more like what they're used to. In the long term, they'll outnumber the Objective-C developers, but the big, expensive apps will still mostly be written in Objective-C, simply because most of them will be new versions of apps that already exist.
BTW, Apple never really treated Java like a first-class citizen; it was always a half-hearted bolt-on language. My gut says that they added Java support under the belief that more developers knew Java than Objective-C, so it would attract developers to the platform faster. In practice, however, almost nobody ever really adopted it, so it withered on the vine. Since then, they have shipped and subsequently dropped bridges for both Ruby and Python.
Any implication that Swift will supplant Objective-C like Objective-C supplanted Java requires revisionist history. Objective-C supplanted C, not Java. Java was never even in the running. And Objective-C still hasn't supplanted C. You'll still find tons of application code for OS X written in C even after nearly a decade and a half of Apple encouraging developers to move away from C and towards Objective-C. (Mind you, most of the UI code is in Objective-C at this point.) And that's when moving to a language that's close enough to C that you don't have to retrain all your programmers.
Compared with the C to Objective-C transition, any transition from Objective-C to Swift is likely to occur at a speed that can only be described as glacial. IMO, unless Apple miraculously makes the translation process nearly painless, they'll be lucky to be able to get rid of Objective C significantly before the dawn of the next century. I just don't see it happening, for precisely the same reason that nine years after Rails, there are still a couple orders of magnitude more websites built with PHP. If a language doesn't cause insane amounts of pain (e.g. Perl), people are reluctant to leave it and rewrite everything in another language just to obtain a marginal improvement in programmer comfort.
Obj-C isn't any better than C in my opinion. But, to each their own.
It is if you're doing any nontrivial amount of string manipulation.
No, they're saying Apple switched because GCC's core wasn't designed in a way that made it easy to extend the Objective-C bits in the way that Apple wanted. And that could well be part of it—I'm not sure.
But I think a bigger reason was that Apple could use Clang to make Xcode better, whereas GCC's parsing libraries were A. pretty tightly coupled to GCC (making it technically difficult to reuse them) and B. licensed under a license that made linking them into non-open-source software problematic at best.
And you know what Mojang's opinion means at this point? Absolutely NOTHING. They can't tell their new owner to honor their intended promises, even if it were written into the deal. All they have to do is replace the boss with someone willing to change the company on Microsoft's behalf and POOF! It's happened with every other developer that's been bought out thus far that came out and said they were told/promised nothing would be changing.
Depends on how good their lawyers are. If they write into the contract a term that says that all rights revert to the original authors if the new owner violates such a term, then yes, they can force the new owners to honor those promises.
Okay, here's a link to the research paper from 2012.
Ebola may not be easy to transmit, but it sure as heck isn't hard to transmit. It's not pedantically known to be airborne, but it is believed to be spread by droplets (e.g. sneezes). There's a very, very, very fine line between the two.
And yes, I can provide citations if you'd like, but it's not like they're very hard to find with a Google search.
Apple's done a lot of work with Grand Central Dispatch (is that the right technology?) to help developers offload as much as possible to the GPU
You're probably thinking of OpenCL. GCD is a pipelining engine for enqueuing work.
Yeah, I was about to say that the reasoning behind the decision was shrouded in mystery, but same idea. Oh well.
The leg pains have nothing to do with exercise or DVTs. Statins are known to cause severe muscle damage (rhabdomyolysis) if too much of it stays in your system for too long a period of time. The pharmaceutical companies say that this side effect is relatively rare, but even if the claimed half a percent is correct, that still adds up to a lot of people when you're talking about a medicine that's as overprescribed as statins are.
That's certainly a reasonable way of looking at it, too. The thing is, though, it's the base price that determines how quickly and broadly something will be adopted; the price of the top model mainly just affects the profitability.
And although the drop happened more slowly, the iPad line, originally starting at $499, now starts at $299 in a smaller form factor, or $399 in a full-size version. One reason its price wasn't inflated much at launch is that it was relatively mature technology when first released—other than software differences, it's basically an iPod Touch or iPhone with a larger screen, and as we all know, making things bigger is a lot easier than making them smaller.
I don't think Apple generally reduces prices. Usually they keep the price and margin steady but improve the hardware.
- The iPod started at $400. Within a year or so, the price had dropped to $300. Four years later, you could get one for $200, and $150 just a year after that.
- The original iPhone started at $500 and $600 (subsidized price). Within a couple of months, they killed the $500 version and lowered the $600 version to $400. One year later, they released the iPhone 3G that started at $200 (for the same capacity as the original $600 version). And of course, you can now get much better iPhone hardware for free.
So then there may be hope for this product, because somewhere out there is a richer/foolhardier version of yourself who thinks of $350 just like you think of $100.
Doubtful. I'm in the Silicon Valley, where we already think of $350 like an average person thinks of $100. It's hard for most people to justify spending more for an accessory than they spent on the phone they're using it with.
Like I said, I'll probably buy one after the inevitable price drop.