| > You are replying to a message that very explicitly didn't say "A bunch of server functionality". Right, let's see... > You can most definitely authenticate requests based on signed tokens and the like Sure, you can, you just have to give up the ability ever invalidate tokens > personalize ads How can this not just be done on the client? > localize content How can this not just be done on the client? > intercept and transform requests How can I implement redirections and security headers here? What context does the Edge function have to do something meaningful here that couldn't have been done on the client? > perform split tests I would prefer to serve my static content from static content hosts with caching capabilities, not Edge functions I am saying this: Edge functions and serverless are loss-leaders for cloud vendors to get you to integrate deeply into their systems. Using them for their tiny, imperceptible gains in the face of the massive engineering efforts (complexity) and risk of vendor lock-in is ridiculous. These use-cases do not justify binding yourself to a cloud vendor. |