What's the relation with gqless?

[borekb]

I'm not very familiar with either but I've seen on Twitter that this is a "rebranded gqless" project (if I understand correctly?!).

Could someone explain:

• The relation of the projects
• Why the new name
• If some technical fundamentals are changing, for example, https://gqless.com/ says "no more code generation" while https://gqty.dev/docs/getting-started shows codegen setup as one of the first things.

I'm not personally familiar with either of the projects but they are something we'd like to evaluate as a GraphQL client for us so I'd like to understand their similarities / differences and their relation in general.

[PabloSzx]

gqty is no more than continuing the development of gqless, I'm the one behind all the rewrite of gqless v2, but the original owner removed me as an admin, and right now he is completely disappeared, any difference in the docs or descriptions are no more than a result of the remake of the website, there is no extra meaning behind everything like if it was worth a conspiracy theory.

The name was basically just a result of brainstorming with @natew and it sounded good and it made sense, there isn't a very deep meaning behind it

[borekb]

Thanks. And about the technical differences, like gqless mentioning type inference instead of code generation while GQty seems to be based on codegen?

[PabloSzx]

no, both are the same, it's the same library but we are continuing its development here, that's it

[bkniffler]

@PabloSzx Appreciate all your work! Could you please add a note to the readme though? I think the situation is worth a notice. Its a bit hard to follow up and understand. "rebranded gqless" doesn't do justice IMHO, but the maintainer removing you as admin and disappearing, with no more maintenance in sight is a good reason to start a different project.