Show HN: Dumbo – Hono inspired framework for PHP

This page summarizes the projects mentioned and recommended in the original post on news.ycombinator.com

CodeRabbit: AI Code Reviews for Developers
Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
coderabbit.ai
featured
Nutrient – The #1 PDF SDK Library, trusted by 10K+ developers
Other PDF SDKs promise a lot - then break. Laggy scrolling, poor mobile UX, tons of bugs, and lack of support cost you endless frustrations. Nutrient’s SDK handles billion-page workloads - so you don’t have to debug PDFs. Used by ~1 billion end users in more than 150 different countries.
www.nutrient.io
featured
  1. Slim

    Slim Framework 4 Skeleton Application

    Can't go wrong with Slim: https://www.slimframework.com/

    But if you're looking for something more modern and interesting, then Hyperf looks pretty cool. They have a mini-framework version you can check out: https://github.com/hyperf/nano

    It does require Swoole, but that is a lot easier to get your hands on these days

  2. CodeRabbit

    CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.

    CodeRabbit logo
  3. dumbo

    A lightweight, friendly PHP framework for HTTP. (by notrab)

  4. nano

    🧬 Nano is a zero-config, no skeleton, minimal Hyperf distribution that allows you to quickly build a Hyperf application with just a single PHP file. (by hyperf)

    Can't go wrong with Slim: https://www.slimframework.com/

    But if you're looking for something more modern and interesting, then Hyperf looks pretty cool. They have a mini-framework version you can check out: https://github.com/hyperf/nano

    It does require Swoole, but that is a lot easier to get your hands on these days

  5. graphql-yoga

    🧘 Rewrite of a fully-featured GraphQL Server with focus on easy setup, performance & great developer experience. The core of Yoga implements WHATWG Fetch API and can run/deploy on any JS environment.

    You're talking about the implementation of the protocol, right?

    That is a good implementation of it, called GraphQL Yoga[0]

    However I'm concerned there is a slight disconnect here. I'm saying that the technical specification of GraphQL does not lend itself to being bad, rather its the failure of developers to really understand its purpose and what its for (its a giant aggregator, with various ways to optimally aggregate things together, depending on what is optimal for a given problem set)

    For that, I recommend becoming more familiar with the specification itself[1] because thats what I'm talking about. The specification (and thus its technical nature) doesn't prescribe anything regarding how you get data on to the graph. Many people equate GraphQL with database problems[2]

    This doesn't mean I don't understand that GraphQL has shortcomings, but all approaches to APIs have short comings. I have found GraphQL has the least amount

    [0]: https://github.com/dotansimha/graphql-yoga

    [1]: https://spec.graphql.org

    [2]: Common complaint I see all the time. I find it stems from a failure to understand how the entirety of GraphQL is meant to work, and some of the mechanics within. Like when to appropriately leverage DataLoader[3], for instance.

    [3]: https://github.com/graphql/dataloader

  6. graphql-spec

    GraphQL is a query language and execution engine tied to any backend service.

    You're talking about the implementation of the protocol, right?

    That is a good implementation of it, called GraphQL Yoga[0]

    However I'm concerned there is a slight disconnect here. I'm saying that the technical specification of GraphQL does not lend itself to being bad, rather its the failure of developers to really understand its purpose and what its for (its a giant aggregator, with various ways to optimally aggregate things together, depending on what is optimal for a given problem set)

    For that, I recommend becoming more familiar with the specification itself[1] because thats what I'm talking about. The specification (and thus its technical nature) doesn't prescribe anything regarding how you get data on to the graph. Many people equate GraphQL with database problems[2]

    This doesn't mean I don't understand that GraphQL has shortcomings, but all approaches to APIs have short comings. I have found GraphQL has the least amount

    [0]: https://github.com/dotansimha/graphql-yoga

    [1]: https://spec.graphql.org

    [2]: Common complaint I see all the time. I find it stems from a failure to understand how the entirety of GraphQL is meant to work, and some of the mechanics within. Like when to appropriately leverage DataLoader[3], for instance.

    [3]: https://github.com/graphql/dataloader

  7. Rack

    A modular Ruby web server interface.

    I've went through a similar journey, with some PHP in the early days, then a lot of Merb/Rack/RoR experience. Though I'd not say PHP is back. I'd avoid it for new projects as there are --IMHO-- much better languages available for free.

    What I really liked from webdevt in Ruby was Rack. https://github.com/rack/rack (gosh I prefer the simplicity of the old logo)

    And I found a Rack-like architecture in "http4k" https://www.http4k.org

    In a way Kotlin can be looked at as a "typed Ruby". Sure Ruby now has optional types, but I believe it's not something easily bolted on later. The whole lang + stdlib should be built in an idiomatic way. Changing the language a lot later usually creates a mess in the stdlib.

    The framework http4k delivers is very similar Hono/Dumbo, but it has a Rack built in as well. Also, http4k is make by functional programming enthusiasts. So it clearly separates logic and data.

    Small request: Please make Hono clickable in the README!

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts

  • Ruby, Rails, Multi-threading e Puma: Como tudo isso se conecta?

    2 projects | dev.to | 11 Feb 2025
  • OAuth 2.0 Authentication with Passport.js: Secure Google, Facebook & GitHub Login

    2 projects | dev.to | 8 Feb 2025
  • Puma 6.6.0 Released – Return to Forever

    1 project | news.ycombinator.com | 28 Jan 2025
  • Implementing Secure Social Login Authentication in Next.js 13+ NextAuth.js

    1 project | dev.to | 16 Jan 2025
  • In-Depth Ruby Concurrency: Navigating the Ruby Concurrency Landscape

    1 project | news.ycombinator.com | 15 Dec 2024