I'm guessing you guys have lots of code review todo!

Anything we can do to help speed the process up? Specific types of unit tests maybe?

Also, a couple of suggestions:

More complicated installer options are a sort of want of mine. It would be nice if I could drop down to custom functions to make the install process more dynamic and user friendly dependent on input.

Also, slight pet peeve, the slider input option seems to have no way of displaying the slider value to the user.

This headline made me think that Cloudflare had finally done what I first assumed Akamai did back in the noughties, before I learned they didn't really have magic tech. :/

Anyway: here's some indirect feedback. It doesn't really apply to your project (which I'm sure will be super useful to other people). I would expect Cloudflare to take the lead in... let's call it widely-distributed-computation. All I want is my code running on your nodes all around the world with an end-to-end ping that is less than 10 ms to the average client.

Cloudflare will need to hire a sandboxing expert for that.

Wait...

Interesting idea. jgc AT cloudflare to tell me more.

As someone who tried building this for the unwashed masses, wait until you have something along the lines of Google Spanner. Developers see amazing gains from edge compute because ZOMG LATENCY, then actually flesh out their apps and start making uncached database calls back to AWS anyway.

EDIT: Yes they lack pricing transparency. Akamai is expensive. As I pointed out, in real world experience less than 5% of the developers I talked to actually could lower response times by moving closer to the client. It's something everyone thinks they need, but the devil is in the implementation details. Akamai hand holds you a lot for your money.

1) What were the interesting technical challenges of evolving the Eager codebase and integrating with Cloudflare since the acquisition?

2) What has surprised you so far in the feedback about developer experience?

The challenges are probably pretty obvious, you have to take this codebase and application which were meant to live on its own and conform it to the way another system works. In the process you have to adapt your deployment, auth, style, etc. to work in this alternative reality. At times it can seem like you spend months working just to get back to the feature set you started with. At others you get to see the vision of an integration you sketched on a whiteboard six months ago become reality and you're blown away that this crazy idea could ever actually work. The definition of 'you' also changed a lot in that process, we went from being a small team to getting support and assistance from dozens of passionate people. It's a very different world where your resources can scale to your vision, instead of having to compromise what you want to build at every turn.

Particularly when you work at a company with as sweeping a vision as Cloudflare, you also get a chance to expand your vision itself. At Eager it was a romantic dream to think we would get on a hundred thousand sites. With our launch today we reach six million. The idea of a $100mm apps fund, or having 60 apps in the store before we even launched, were not things which startup-Eager could have pulled off.

My biggest surprise is gonna be a little silly but it's it's when someone builds a really great app without any help or guidance. As much work as you put into the API or docs it's always a little shocking when someone builds something from scratch on the platform you work on every day, and it works well, out of the box.