> since it push on semantics that can only be run on Cloudflare infrastructure

No, workerd and its semantics are not exclusive to Cloudflare infrastructure. People really do run it in production without using Cloudflare at all (I really wish I was allowed to say who because one of the users is hilariously ironic...).

Ryan's and Bert's core focus at Cloudflare is going to be making the self-hosting story better.

This was emphasized in the blog post: https://blog.cloudflare.com/deno-joins-cloudflare/

▲

syrusakbary 2 hours ago | parent [-]

Thanks for chiming in Kenton.

> workerd and its semantics are not exclusive to Cloudflare infrastructure

I believe they are. You may be able to run workerd, but you can't run D1 (Sqlite alternative), you can't run KV or Queues (please correct me if I'm wrong).

All those are primitives that already exist in the non CF world: KV can be easily redis/memcached. Queues, Kafka and so on. I believe that a system that reuses those would be stronger.

> I really wish I was allowed to say who because one of the users is hilariously ironic

Ok, this peaked my curiosity. Would be great if you could share it!

▲

kentonv an hour ago | parent [-]

> You may be able to run workerd, but you can't run D1 (Sqlite alternative), you can't run KV or Queues (please correct me if I'm wrong).

Details remain to be worked out, but part of the goal of the project is to make all these interfaces plugable with reference implementations that can sit on common infrastructure.

In fact, celld has already done a lot of this.

> Ok, this peaked my curiosity. Would be great if you could share it!

You'll have to find me in person over drinks somehow. ;)

	▲	tibozaurus 5 minutes ago \| parent [-]
		Is it the triangle ?