102
Man, FB is horridly optimized
(sh.itjust.works)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 20 Nov 2025
102 points (94.0% liked)
Programming
26482 readers
398 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
GraphQL has all the right combination of abstracting a really hard problem, ignoring the hard details, and giving you enough toggles to pretend you can solve the worst problems that makes hyping it really, really easy.
I’m mostly into it for the strong typing, self-documenting nature of it. In my own GraphQL APIs I’ve done a pretty great job of avoiding common pitfalls.
I’m a Ruby on Rails developer currently developing a service that’s basically ripped out of another Ruby on Rails app and the legacy data is just crazy bad — a lot of it has to do with poor validation but it’s understandably easy to get to that point in a dynamic language like Ruby if you’re not careful.
I also manage a REST JSON:API and it’s just so bulky and horrible to deal with. The tooling is barely there and it’s way overly complicated compared to GraphQL — the concept of “only query what you need” is fantastic.