An interesting dive into the long-term complications and issues that Matt has come across whilst using GraphQL. From self-professed "hype train member" for the technology to now considering it a niche tool only beneficial in specific areas, it's an interesting read, though largely boils down to "GraphQL is probably too complex to manage yourself", which means if you're outsourcing that to a third party already, few of the criticisms should matter to you. Still, it's nice to see a more nuanced take and it provides some excellent points around security and performance that are absolutely worth being aware of.
- Source
- Link to Original 🔗
- Published
- Categories
- Nuts & Bolts
- Tags
- GraphQL
Explore Other Notes
⬅ Newer
Digital litter picking
The idea here is far from revolutionary, but I really like the naming and overall approach. Digital litter picking: a small, scalable, civic good that you can just do. …
Older ➡
Stacking grids without media queries
A very clever technique of using combinations of flex-basis, asymmetrical flex-grow, or (for Grid) some quirky minmax() magic to generate flexible layout shifts that, in practice, …
- <!DOCTYPE html> <html> <head> <title></title> </head> <body> <p>An interesting dive into the long-term complications and issues that Matt has come across whilst using GraphQL. From self-professed "hype train member" for the technology to now considering it a …</p> </body> </html>
- Murray Champernowne
