Thanks for the thoughtful reply. I agree with a lot of how you analyze it.
I guess what feels odd is that while so much of the web is co-dependent on different products or services, that is still different from centralized vs. decentralized. So when a network is decentralized, yet the keys to it's main highway remains in the control of one person (or group) that runs a server and manages a domain, it feels a bit contradictory.
having worked with both I think each lends itself better to different projects. Amplify gives you the option to work both with REST or GraphQL, however you then have to go through all the steps of setting up a CRUD api. That part comes out of the box on 8base, with things like relational filtering, pagination, etc.
The way I think of these things is always that the more tools you have in the tool-chest, the more things you can build. It's NEVER wrong to learn more or dive deeper. But just because you might know-how and be capable of building a house by sawing down your own lumber and smithing your own nails, doesn't mean you wouldn't want to order some parts pre-fab - or at least go to the hardware store!
I'd try logging in and creating a data-model for your project. All the GraphQL operations will be generated from that so you can start using the workspace API. Whatever application you're building than then connect through there.
This is awesome! I'm stoked to see the GraphQL community getting this polished of a tool. Chris Coyier wrote on css-tricks the other day about the best GraphQL API being one you write yourself, which is super true as the ones offered by headless CMSs and the like aren't ever customizable enough. I can't imagine a spec though that can be met between what 8base is generating + custom resolvers.
This is actually super useful sha666sum! It's interesting looking at the difference between the two too. Where Visual Studio IDE is super direct, and Visual Studio spans a number of use cases. I feel like that's where I'm getting caught in the middle of.
I guess what feels odd is that while so much of the web is co-dependent on different products or services, that is still different from centralized vs. decentralized. So when a network is decentralized, yet the keys to it's main highway remains in the control of one person (or group) that runs a server and manages a domain, it feels a bit contradictory.