←back to thread

Show HN: Dumbo – Hono inspired framework for PHP

(github.com)
76 points notrab | 1 comments | 18 Nov 24 07:37 UTC | HN request time: 0.209s | source

Hey HN, I last PHP professionally over 15 years ago, and I loved it. I switched to Ruby on Rails, then Node/Go/React/GraphQL as there was a lot more demand for those roles. However, PHP is back!

In true JavaScript fashion, I decided to learn PHP again by building a framework to put all the pieces together in my brain.

I absolutely love Hono.dev, and decided to base the PHP framework on that. Dumbo isn't intended to compete with Laravel, Symphony or Slim, if anything, it's something people can use in production, but also contribute to and be used as a learning resource for others.

Show context
dzonga ◴[18 Nov 24 13:16 UTC] No.42172050[source]▶
I wish the market didn't determine the technologies we get to work with. because at times the market can be wrong due to incentives.

e.g the market was wrong on graphQL.

btw Hono is cool, but found the api surface area insufficient for my node.js usecases.

replies(2): >>42172914 #>>42217711 #
no_wizard ◴[18 Nov 24 15:02 UTC] No.42172914[source]▶
How was the market objectively wrong on GraphQL?

I ask a a REST turned GraphQL advocate to be clear but criticisms I hear tend to be opinions or issues with specific implementations but not ones based on the technical shortcomings of the technology

replies(3): >>42173003 #>>42174801 #>>42184153 #
davzie ◴[18 Nov 24 15:11 UTC] No.42173003[source]▶
I can't comment on all the shortcomings and this may be reflective on my lack of experience with different implementations, but doesn't using GraphQL basically just enable a tonne of unoptimised database queries to occur that, at scale, could cause some serious load issues?
replies(1): >>42173029 #
no_wizard ◴[18 Nov 24 15:13 UTC] No.42173029[source]▶
GraphQL says nothing about databases at all. Resolvers can get resources from anything, they’re agnostic.

None of that is inherent to the technology but it’s a common folly among developers. This is an issue with REST too but it can be more obfuscated

replies(1): >>42173357 #
ITB ◴[18 Nov 24 15:37 UTC] No.42173357[source]▶
If a certain arrangement makes it more likely to write bad queries, and it requires extra care to write optimal queries, then it’s a worse interface to a database. I bet for really database intensive applications graphQL adds more work than it saves.
replies(1): >>42173807 #
no_wizard ◴[18 Nov 24 16:15 UTC] No.42173807[source]▶
It’s not though. Especially since GraphQL makes no mention of databases. It’s a resource agnostic protocol.

This isn’t a technical issue with GraphQL. It’s a culture issue among developers who shoehorn GraphQL and don’t use it appropriately

As someone who works on very database intense application GraphQL saves me more work than its ever caused.

replies(2): >>42174121 #>>42217730 #
1. endofreach ◴[22 Nov 24 22:01 UTC] No.42217730[source]▶
> GraphQL makes no mention of databases. It’s a resource agnostic protocol.

So the QueryLanguage is just marketing?