With RTK Query, you usually define your entire API definition in one place. This is most likely different from what you see with other libraries such as swr or react-query, and there are several reasons for that. Our perspective is that it's much easier to keep track of how requests, cache invalidation, and general app configuration behave when they're all in one central location in comparison to having X number of custom hooks in different files throughout your application.

we’re working on improving WebAssembly to enable support for more languages. At present, it works OK for C/C++/Rust. Unfortunately, Go is a challenge to get working on Workers right now due to requiring a large code footprint (garbage collector, green threads, etc.) and wanting to allocate too much memory. We’re working on solutions for these problems, such as allowing multiple WASM apps to share a single copy of a common runtime, but this is a complicated project that will take time.

Explicit and consistent conventions even if they require more effort are worth it

HMR update speed deteriorates significantly as the size of the application grows