3 ms·
dude, the point was that flow/ts anything out of your preferred ecosystem... it's not going to work as a general solution because 1. nobody wants the bs out o
by verdverm 3y ago
dude, the point was that flow/ts anything out of your preferred ecosystem...
it's not going to work as a general solution because
1. nobody wants the bs out of that "ecosystem" (applies to any language specific ecosystem)
2. it's not implemented in all the other languages and therefore not portable. Who's going to write all the parsers for your "solution"?
If all you write is JS/TS, you should really try out some other languages so you get a better perspective.
This is exactly why we have standards like OpenAPI... your solution would be a single ecosystem solution.
How would one put things like authentication, examples, and response codes in their public schema under your "solution"?
- mirekrusin 3y agoGraphQL has similar type system and it is portable.
- verdverm 3y agoyaml & json are more portable, with codecs available in many stdlibs. You can decode directly into language types in most cases CUE is the future I hope for
- mirekrusin 3y agoYes, cue is awesome.
- verdverm 3y agoYou might like this thing I'm working on then https://youtu.be/XNBqBWO4y08 https://youtu.be/XNBqBWO4y08