Code generation is becoming really important in Go.<p>Why even use an ORM when <a href="https://sqlc.dev/" rel="nofollow">https://sqlc.dev/</a> will generate everything from vanilla SQL?<p>Why make the frontend team write a Typescript client when <a href="https://goa.design" rel="nofollow">https://goa.design</a> on the backend will produce an OpenAPI schema they can just point a <a href="https://openapi-generator.tech" rel="nofollow">https://openapi-generator.tech</a> at?<p>Why write out GraphQL boilerplate when <a href="https://github.com/99designs/gqlgen" rel="nofollow">https://github.com/99designs/gqlgen</a> will take your GQL typedef and generate it all for you based on how you want it to look.<p>Why write validation rules when you can just define your input struct and let <a href="https://github.com/mustafaakin/gongular" rel="nofollow">https://github.com/mustafaakin/gongular</a> generate the rest for you?<p>Honestly, I'm loving this. I want to focus on the entities and business logic - not writing yet another handler/resolver for basic auth + CRUD work.
Seems like strange choices for "CloudQuery vs Others". Why not compare against FiveTran, Airbyte, Meltano or other EL tools?<p>Also, It'd be nice to know what the transfer protocol is like. What format is used to transfer between a Source and Destination?
So golang macros when?<p>Honestly the language is the new JS and just another one to remind us how miserable software can be with half baked enterprizy solutions to just get the job done faster.