"Well there are super technical reasons for this."
Okay, sure, fine, whatever. Magically @fastly has worked around that, but I'll suspend credulity.
Lambda@Edge then becomes an implementation detail. Why do I have to worry about it instead of you?
Add "Set static header" text fields to the other 4000 CloudFront distribution options, take my input, and custom deploy Lambda@Edge functions or pixie dust or six pagers or whatnot, just inject the headers without making me care about how.
"Pull requests welcome" is how you're asked to volunteer, "use a Lambda function" is how you're asked to pay to volunteer.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
I don't see what @chetanp does with respect to GCP, but it's a mighty big industry. I suspect we're both pawing at different parts of the elephant.
The single biggest impediment to @azure near-term looks like Old Microsoft playing stupid licensing games to win stupid prizes.
But consider this for a second: You're a developer puttering around in your idle hours. Your @azure free tier resources / limits are a function of your @GitHub activity (social or otherwise). Suddenly it's gamified and profoundly compelling.
First I have to verify a phone number (Google Voice not allowed), now they want a credit card as well. Which box do I leave blank to *not* get information, tips, and offers?
So far this isn't the experience I had hoped for.
Now to figure out where to generate API keys. Security Center? Doesn't look like it.