My mistake to jump the gun. It looked like machine executor was just a porting of circle 1 (which in some way is: similar syntax, features, etc). Moreover, comments like:
Seemed to hint at the docker executor, not the machine one. Overall, it seems that’s what you guys are pushing more, since it’s the biggest novelty of v2.
As usual, frustration in a specific moment didn’t help my reasoning, I apologize for that. On your end probably additional documentation about the machine executor would be helpful, since the info is very sparse, but I am sure you are already working for now. Also, the “using docker” section of the documentation only speaks about docker executor, so it seems that that is the suggested way, which to go back to my first comment seem a little bit haphazard (that is, docker executor with remote docker environment cannot make use of many of the features of the docker executor). In the end of course is up to us to decide what better fits our needs individually, but I am not sure what you guys suggest is better suited for this. docker executor w/ remote docker engine, vs machine executor? I understand the lack of documentation since this is still beta, probably this is a good opportunity to clarify this?