Good point. Cars will still be valuable for road trips, but lots and lots of people will choose to skip car ownership and just settle for local, self-driving travel.
Maybe there will be a stratified market for rental self-driving cars; one for "just this trip" and another for "five days of exclusive use for a road trip."
I remember building a hackintosh about 6 years ago, has much changed since then? It was a lot of fun and a lot more challenging than a regular Windows PC build.
I think a faxed signature counts as a "wet" signature. Also it's easier to sign then feed into a fax machine than:
- sign
- scan (usually sent as a weird filename to your corporate email)
- save the attachment, rename the file, create a new email, attach the file, send
Doesn't Dropbox run on S3? Or is that the company that recently moved off AWS into their own datacenters? If so that was a good case study. (I'm an all 5 certified AWS guy and while I love it, I like seeing the counterexamples to keep my Kool-Aid ingestion in check).
Also nice is the in-service rollover, so you can roll funds directly from the company's 401(k) plan into your self-directed IRA or whatever multiple times per year, instead of when you leave.
Yah but you can still put in your own pre-tax money. You are stuck in the BS high expense ratio funds that some slick "benefits consultant" sold to HR/management for those 2-3 years, but as soon as you leave, you can roll over those 401(k) funds into a self-directed Roth IRA.
I salute you for your commitment to watching Fox News. After Trump's election I said I was going to consume more of the other-side-centric media because I wanted to understand how this F'ing happened. I can't, though, it's too painful. So I salute you.
The thing is, an S3 bucket policy is not an IAM policy. It's a bucket policy. They use the same language, format, and syntax, but they are not called the same thing.
Isn't the "Principal" element only a part of S3 permission policies, not IAM? In IAM the "principal" is implied, it's the user to which the policy is attached. Edit: I see you explain well into the article, but I believe the title of the article could be improved.
I'm still interested in how to merge features like AWS Autoscaling with Docker to right size the underlying infrastructure for the amount of container work going on.