4 ms·

Making a regular api

by JohnHaugeland 4y ago

endisneigh 4y ago
A regular api poorly implemented will have all the same cons and none of the pros.
- geysersam 4y ago
  Just make a perfect api without any drawbacks.
  - deleted 4y ago
    [deleted]
  - endisneigh 4y ago
    GraphQl has a set of trade-offs. REST also has trade-offs. Bespoke RPC calls have trade offs. It's as if the entire discipline is an exercise in selecting trade offs or something.
    - anotherhue 4y ago
      Well put. Problem is we can get emotionally invested and tie our identities to these systems in a way that we couldn't if we were comparing the trade-offs between 18/10 and 18/12 inox steel.
- deleted 4y ago
  [deleted]
- JohnHaugeland 4y ago
  > A regular api poorly implemented will have all the same cons and none of the pros. Okay, so don't make a poorly implemented one? Also, no, it kind of won't. Let's look at what they are again . "It is actually a pain to use" Not an API characteristic . "you'll have to manage two or more type systems if there are no code first generates in your language" Not an API characteristic . "It doesn't support map/tables/dictionaries." Not an API characteristic . "No clear path for Api versioning" Not an API characteristic . Looks like it's actually zero for four
  - gabereiser 4y ago
    In order to build a properly implemented one, one must first learn to build one. I find most people jump onto graphql because they see the volume of work to create crud endpoints for all of their models and decided to punt.
    - legalcorrection 4y ago
      It’s a false promise. You’re just moving the complexity elsewhere, into wiring this ridiculous graphql infrastructure together and making it actually do what you want in all but the simplest/tutorial-like scenarios.
      - intelVISA 4y ago
        Seriously. I sometimes think I'm visiting a satirical alter realm when I see these obtuse systems that end up requiring more cognitive energy to glue together than the regular version in <lang of your choice here> being praised rather than derided.
        lelanthran 4y ago
        > I sometimes think I'm visiting a satirical alter realm when I see these obtuse systems that end up requiring more cognitive energy to glue together than the regular version in <lang of your choice here> being praised rather than derided. You're lucky, you're only visiting. I'm working in that alternate reality :-)

Making a regular api

endisneigh 4y ago

A regular api poorly implemented will have all the same cons and none of the pros.

geysersam 4y ago
Just make a perfect api without any drawbacks.
- deleted 4y ago
  [deleted]
- endisneigh 4y ago
  GraphQl has a set of trade-offs. REST also has trade-offs. Bespoke RPC calls have trade offs. It's as if the entire discipline is an exercise in selecting trade offs or something.
  - anotherhue 4y ago
    Well put. Problem is we can get emotionally invested and tie our identities to these systems in a way that we couldn't if we were comparing the trade-offs between 18/10 and 18/12 inox steel.
deleted 4y ago
[deleted]
JohnHaugeland 4y ago
> A regular api poorly implemented will have all the same cons and none of the pros. Okay, so don't make a poorly implemented one? Also, no, it kind of won't. Let's look at what they are again . "It is actually a pain to use" Not an API characteristic . "you'll have to manage two or more type systems if there are no code first generates in your language" Not an API characteristic . "It doesn't support map/tables/dictionaries." Not an API characteristic . "No clear path for Api versioning" Not an API characteristic . Looks like it's actually zero for four
- gabereiser 4y ago
  In order to build a properly implemented one, one must first learn to build one. I find most people jump onto graphql because they see the volume of work to create crud endpoints for all of their models and decided to punt.
  - legalcorrection 4y ago
    It’s a false promise. You’re just moving the complexity elsewhere, into wiring this ridiculous graphql infrastructure together and making it actually do what you want in all but the simplest/tutorial-like scenarios.
    - intelVISA 4y ago
      Seriously. I sometimes think I'm visiting a satirical alter realm when I see these obtuse systems that end up requiring more cognitive energy to glue together than the regular version in <lang of your choice here> being praised rather than derided.
      - lelanthran 4y ago
        > I sometimes think I'm visiting a satirical alter realm when I see these obtuse systems that end up requiring more cognitive energy to glue together than the regular version in <lang of your choice here> being praised rather than derided. You're lucky, you're only visiting. I'm working in that alternate reality :-)