Skip to main content

Philosophy

Model-written

contextclaimresult

Philosophy

Philosophy section introduces Hono's concept and philosophy

In this section, we talk about the concept, or philosophy, of Hono.In this section, we talk about the concept, or philosophy, of Hono.This section discusses Hono's concept and philosophy It sets the stage for the motivation and design principles that followThis section discusses Hono's concept and philosophyHono's concept

Motivation

Hono was created to fill a gap on Cloudflare Workers

At first, I just wanted to create a web application on Cloudflare Workers. But, there was no good framework that works on Cloudflare Workers. So, I started building Hono.But, there was no good framework that works on Cloudflare Workers. So, I started building Hono.Hono was started because no good framework worked on Cloudflare Workers The author wanted a web app there but found no suitable framework, so he began building HonoHono was started because no good framework worked on Cloudflare WorkersCloudflare Workers

I thought it would be a good opportunity to learn how to build a router using Trie trees. Then a friend showed up with ultra crazy fast router called "RegExpRouter". And I also have a friend who created the Basic authentication middleware.I thought it would be a good opportunity to learn how to build a router using Trie trees. Then a friend showed up with ultra crazy fast router called "RegExpRouter". And I also have a friend who created the Basic authentication middleware.Building Hono started as a learning opportunity for Trie trees and later got a fast router and middleware from friends The author used it to learn Trie trees, then a friend provided RegExpRouter and another made basic auth middlewareBuilding Hono started as a learning opportunity for Trie trees and later got a fast router and middleware from friendsTrie trees

Using only Web Standard APIs, we could make it work on Deno and Bun. When people asked "is there Express for Bun?", we could answer, "no, but there is Hono". (Although Express works on Bun now.)Using only Web Standard APIs, we could make it work on Deno and Bun. When people asked "is there Express for Bun?", we could answer, "no, but there is Hono".Using only Web Standard APIs, Hono works on Deno and Bun This allows answering whether Express exists for Bun with "no, but there is Hono" though Express now works on BunUsing only Web Standard APIs, Hono works on Deno and BunWeb Standard APIs

We also have friends who make GraphQL servers, Firebase authentication, and Sentry middleware. And, we also have a Node.js adapter. An ecosystem has sprung up.We also have friends who make GraphQL servers, Firebase authentication, and Sentry middleware. And, we also have a Node.js adapter. An ecosystem has sprung up.An ecosystem has sprung up around Hono, including GraphQL, Firebase auth, Sentry, and a Node.js adapter Friends contribute middleware and adapters, making Hono more capableAn ecosystem has sprung up around Hono, including GraphQL, Firebase auth, Sentry, and a Node.js adapterecosystem

In other words, Hono is damn fast, makes a lot of things possible, and works anywhere. We might imagine that Hono could become the Standard for Web Standards.In other words, Hono is damn fast, makes a lot of things possible, and works anywhere. We might imagine that Hono could become the Standard for Web Standards.Hono is damn fast, enables many things, and works anywhere, possibly becoming the Standard for Web Standards The author imagines it as the standard for web standardsHono is damn fast, enables many things, and works anywhere, possibly becoming the Standard for Web StandardsHono