390 karma · joined February 14, 2019
Things like:
- Developer onboarding and review (Legal and KYC) - App submission and review (standard, priority, exposure, etc) - App distribution (origin storage and download) - Push notifications
I believe that Apple should be forced to change, I just don’t know what we all should expect
It's just not worth the overhead in people and hardware to try to be surgical in your approach - you don't win anything. It's the closest thing to working at the DMV for tech.
Notes, cc:Mail, Groupwise, Exchange, Sendmail, Exim, qmail, postfix, etc... I have no interest in running my own email ever again.
The real issue is how that data get's into S3 in the first place and what else you need to do with it.
S3 and DynamoDB are the real moats for AWS.
I kinda hate that the new MacBook Air went back to a MagSafe charger for this reason.
Internal Tech Emails is a goldmine of letters, threats, and lawsuits back and forth.
And learned nothing from the experience
Sure you have a contract but you need to enforce it. So you have to sue which takes time - a lot of time.
Then you “win” but the other party can still not pay, or they could appeal - back to court and even more time.
The landlord has an iron clad contract sure - but Twitter has what they want ($) and the leverage as a result.
It was the way to do it, and very easy to manage.
As a postmark and dmarc digest customer I hope the services don’t see drastic changes to our detriment.
Unionization at a single store seems extremely risky for labor
Especially when the company is going to be weighing the potential of more following
As much as I want to hate this, it's actually genius and elegant in its simplicity.
Kudos to the team for doing this the best way possible. Making a public announcement, refunding money, providing ample time to migrate is amazing.
Keep your heads up
Also depressing how this is so far beyond what the majority of people are aware of / are willing to do. I worry what this means for Cybersecurity in general.
Apple’s behavior is BS and they need to be forced to allow competition
They’ve done it to themselves
What caused me to leave?
- They aren't global portfolio aware. Bonds belong in tax advantaged accounts, then taxable. If you've maxed out your 401k/IRAs in Bonds that $ as an absolute percentage should be accounted for in your taxable portfolio construction.
- They don't let you opt out of asset classes. Aka I don't want additional REITs because I have RE exposure already.
- They overly hype tax loss harvesting. It's good to have, but a byproduct of portfolio management not the goal.
- They launched and pushed risky products as a way to increase their fees.
Once you understand what's going on under the hood this isn't complicated to manage yourself with a few ETFs/MFs.
(The direct indexing is awesome and would love to have that back)
Maintainers should be able to do whatever they want either their code
But if they vandalize their modules that should be a lifetime ban from the registry
It’s pretty obvious that node needs a better method for dealing with this by now
I've had this argument too many times to count. Every page view does not need to be dynamic per user request. Creating a sane cache policy reduces origin resources, servers, cost, etc... and surprise gives a better user experience at the same time.
It doesn’t look like we’ll ever get beyond the politics that would make small scale <10MW installations economically feasible.
It’s really a shame.