Co-existence of GDK and GCK

From our %13.3 retro:

Jean du Plessis: Is it worthwhile having both the GDK and GCK? Could we not rather settle on one and put the combined effort into one to make that much better rather than have two separate systems? When team members spend a lot of time getting the GDK up and running that can have a big impact on capacity for the milestone.

• Vote (increment the counter pls): 3
• Chad W: I think they have different goals. E.g., if mac users are OK dealing with local dependencies to avoid the docker filesystem performance hit and docker complexity, they can choose GDK. If linux users don't want to deal with local dependencies, they can use GCK since they don't have the filesystem performance hit. There's also other issues like IDE integration perhaps not working as well with GCK.
• Chad: But I do have problems with GDK being broken/rotten after revisiting it after a few weeks away.
• Changzheng: It would be better to collect more feedback from broader audiences.
• Chun: Shall we compile a list of top pain points to prioritize the improvements?
• Christie: The UX department uses GDK a lot
• Christopher: I’m for follow up here. I don’t think the DRI for this is on the call. Chun, you want to track them down for an action item for feedback. => Chun: Action item registered below for Lukas.
• Clement (non verbal): gitlab-compose-kit#19 (closed) maybe something to check out for some previous conversations around GCK vs GDK co-existing
• Mek: Wider community is using the GDK.

So there is an alternative development environment, the gitlab-compose-kit based on docker-compose.