Replies: 1 comment 1 reply
-
Hi @jcjp, appreciate the curiosity to compare h3 with other frameworks. Frankly, H3 is not purposed to compete or be compared, but is specially focused on being minimal, single-purpose (one job, do it well) and composable so it can be integrated with anything else with minimal impact. We moved from Node.js APIs to Web to make H3 even more composable with modern libraries. Either Elysia or Hono apps can be mounted into an H3 instance for when their specific features are needed, or we can make community integrations for any RPC libraries instead of choosing one or making another inside H3. Validation is another example; H3 only opted in to support standard-schema-based validators. While I fully agree we probably need to explain these thoughts, we probably shouldn't try to compare H3 with other libraries but make more "H3 with X" integrations documented. If you have any other questions to clarify, I would be more than happy to answer & cheers. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Sorry but you might have this already but do you have a table comparison of features vs Hono, Elysia, Express and other popular backend frameworks? Hono seems to have feature for RPC support for service to service of backend to backend communication, do you have anything that is similar?
Beta Was this translation helpful? Give feedback.
All reactions