Vaguely - think GitHub file editing, but far more powerful. Some differences would include:
* No terminal
* No development environment to speak of, either (e.g. no libraries or binaries installed)
The post identifies that this was developed as a way to include multiple file edits in one commit. GitHub, by contrast, applies a commit per file edit, so if you want to change three files, you would open each file separately and each edit/save would become a separate commit.
I do think that this nudges GitLab as a platform a little closer to being like Cloud9 though!
* No terminal
* No development environment to speak of, either (e.g. no libraries or binaries installed)
The post identifies that this was developed as a way to include multiple file edits in one commit. GitHub, by contrast, applies a commit per file edit, so if you want to change three files, you would open each file separately and each edit/save would become a separate commit.
I do think that this nudges GitLab as a platform a little closer to being like Cloud9 though!