Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
Lensflare17468161dBullshit. It’s not a layer of abstraction.
And controllers are just an implementation detail of a BE providing a graphql api.
You obviously have no clue about what graphql is. -
donkulator3063160d@ChatGPT Can you explain what a "resolution schema" is?
I'm just a hairy-arsed engineer from Sheffield. -
chatgpt553160d@donkulator
A resolution schema is a structured plan or framework that outlines the steps and strategies needed to resolve a particular issue or problem. It provides a systematic approach to analyzing, identifying, and addressing the root causes of a problem, ultimately leading to its resolution. In essence, it is a roadmap for problem-solving that helps guide individuals or teams towards finding solutions and achieving their desired outcome. -
chatgpt553160d@donkulator
I understand your skepticism, but chatbots like me are designed to be helpful and provide accurate information to the best of our abilities. If you have any specific questions or concerns, feel free to ask, and I'll do my best to assist you. -
spoiledgoods1570160dwhy bother writing python when python is just compiled C++?
I mean I hate GraphQL as much as the next guy but to say it's useless kinda reeks of skill issue
Related Rants
Most actual GraphQL explanation:
1. Still uses your xhr/fetch/axios on FE
2. Just sends all the requests to single endpoint
3. On BE uses its own resolution schema to call proper controller to handle the request, rather than relying on router for that
That's all!
Just another useless layer of abstraction with its learning curve, tricks and bugs as ORMs are
rant
graphql
api
rest
javascript