| ▲ | krosaen 4 days ago | |
This looks pretty awesome, and excited it's not only a cloudflare product (Cap'n Web exists alongside cloudflare Workers). Reading this section [1], can you say more about: > as of this writing, the feature set is not exactly the same between the two. We aim to fix this over time, by adding missing features to both sides until they match. do you think once the two reach parity, that that parity will remain, or more likely that Cap'n Web will trail cloudflare workers, and if so, by what length of time? [1] https://github.com/cloudflare/capnweb/tree/main?tab=readme-o... | ||
| ▲ | kentonv 4 days ago | parent [-] | |
I think we'll likely keep them pretty close to in-sync, at least when it comes to features that make sense in both. If anything I'd expect Cap'n Web to run ahead of Workers RPC (as it is already doing, with the new pipeline features) because Cap'n Web's implementation is actually much simpler than Workers'. Cap'n Web will probably be the place where we experiment with new features. | ||