Ironically, GitLab pages ended up not working very well for me. It was nigh impossible to add a cert to a custom domain. I ended rewriting the CI pipeline to push to Firebase.
In the past, people would request ftp/ssh. Setting up git and auto-deploy with custom scripts didn't scale well. Our clients seem very content with WebIDE. They can do quick edits and barely know they are using git.
The idea is that there's a lot of different users using git and I want to make it accessible for everyone.
I was able to use Web IDE to edit a couple files including a `.gitlab-ci.yml` and kick off a continuous integration job from my iPad 6th Gen. I hit a snag with the Merge Request, but the commit worked okay. For now it would be a little cumbersome to rely on as a primary development workflow, but it's fun as a proof of concept.
Editing multiple files is a pain though, you'd need one per commit, so this seems to solve that for me.
Git has a super high learning curve for simple edits...
The Web IDE thing is something more sophisticated.
See for more information https://gitlab.com/gitlab-org/gitlab-ce/issues/47307 and https://gitlab.com/gitlab-org/gitlab-ce/issues/46122 for example in how we are improving this starting with 11.1
Git, like God, is good :) But even, over time, God has evolved and gotten more accessible.
This will make it easier for non-techies to edit product requirements, without deep knowledge of git.
https://gitlab.com/gitlab-org/gitlab-ee/issues/5981
Once this is completed/implemented, our entire company will be migrating our old school document system to GitLab, using static pages, merge request approvals and this Web IDE.
If push comes to shove, I'll have to fork and do it myself ;)
If I don't want to keep using Sublime Text, I just do Windows key + R something else.
Moving away from time-sharing platforms is a complete different story.
According to an Xoogler acquaintance, he used a web IDE for all his development; I'm not sure how widespread this is in Google, but the answer to your question could be "lots".
(Any Googlers want to chime in with estimates on % of devs using web IDEs?)
It helps that there's a single source repo to work from, a remote filesystem for all source code whether working remotely or local that syncs immediately, and a single build system.
For me, I do all work from my laptop in the web IDE and save harder or larger things for when I'm at my desk. It's pretty great that I can start a change in one, then switch to the other seamlessly e.g. write the bulk in an IDE, then make changes in response to comments via the web IDE.