571 karma · joined September 9, 2012
For the ones that need more performance, it can be a dealbreaker to go so long without updates.
For the ones that have their needs are met today, there's a very clear signal now that if your needs ever grow, Apple won't be there to meet them.
Current revenue doesn't necessarily say anything about future decline, you need to look deeper than that.
I don't understand why you think the article is poorly written, but I certainly can understand and agree with the authors concern. I'm not sure how it's possible to not share that concern after the lack of updates to the desktop line.
I think we won't see how Apples management really works until there's a new product space that Apple entirely misses, and I don't think we've seen that yet (it could be AI, VR, or something entirely different we haven't thought of). If they miss that just like Microsoft did in the tablet / mobile space, then we can start comparing Tim Cook to Ballmer.
On the other hand, last time he picked a successor in the 80s he picked the wrong guy.
What he warns against is betting too early on core technologies like service discovery, deployment systems (Docker etc), database systems (MongoDB) And from reading HN posts, it sure seems like there's no shortage of people being burnt by that.
My experience has often been that whatever feature is lacking in the language tends to be made up for by huge code bases that are impossible to navigate, or using frameworks that abuse whatever dynamic features you have in the language horribly with added complexity in tooling and debugging.
They also allow you to manually get out of the UPDATE_ROLLBACK_FAILED state, which was usually where you needed to contact AWS.
Cloudformation also supports Lifecycle events. They are a bit complicated to set up right, but they allow you to tell CloudFormation how to wait and how to proceed in response to resource signals (for instance, the deployment can wait or roll back if new instances in an ASG fail to be deployed). Terraform has none of that. It has "create before destroy", and "depends on", but that's about it AFAIK. If CloudFormation fails it will at least attempt to roll back to a sane state (and usually succeeds). Terraform will give up and leave you to clean up the mess.
Apart from that, Terraform has an advantage because of the modularity, ability to easily bring resources in, reference other resources in remote states etc.
And of course, the more you associate and interact with groups that fit your opinions and interests, the more Facebook and other ad-supported services will try to prioritize showing you those posts, so the echo chamber effect is amplified.
And when you step out into the real world, you'll be inclined to think of others that don't share your "informed" opinion as uninformed or naive, after all you have seen all this evidence to back you your opinions and theories. [Edit:spelling]
That said, the problem with debugging stands (for AWS lambda, at least).
Does it matter more that there's no duplicate particles (ie. no changes of a copy being made)?
In that case, you could device a teleport machine that makes sure to read the state "bit by bit" (particle by particle), then destroys the original particle before creating a new particle in another location. How different would that be compared to what's normally happening to your body?
What defines "you"? The matter you're made of?
Is it a particular arrangement of that matter? (Would you care if your neurons were replaced one by one, while keeping the same arrangement?)
Is it your memories, your thoughts, your inclinations?
Or is it something else?
(Maybe this whole discussion is less interesting to Buddhists trained in not-self thinking. :)
If I didn't consent to the cloning, that would complicate things. Likewise, my trust in the cloning process would proably affect my decision.
Or put it another way, let's say we live in a software simulation. Do you care whether our sysadmins live migrate our simulation over to a new Alien Web Services instance?
I think the real reason for Apples worry is that they want people to trust the smartphones for way more then just payments, for instance Health information. And people might just end up much more reluctant to do so if they know the phones are easily hackable.
So clone the last release version you trusted, build that from source and be happy?
"On our production frontend machines, SSL/TLS accounts for less than 1% of the CPU load, less than 10 KB of memory per connection and less than 2% of network overhead. Many people believe that SSL/TLS takes a lot of CPU time and we hope the preceding numbers will help to dispel that." - Adam Langley, Google
Getting an SSL certificate used to be a cost, but that's taken care of now by https://letsencrypt.org/.
So the "little more" part is the difference between some art student being able to create something cool vs. giving up after three days banging his head against a wall. But when you're an expert in a field it's hard to appreciate that.