Web-based editor(docs.github.com)
docs.github.com
Web-based editor
https://docs.github.com/en/codespaces/developing-in-codespaces/web-based-editor
301 comments
I am still proud of [github1s](https://github.com/conwnet/github1s)
No Credits given :( => https://github.com/conwnet/github1s/issues/346
No Credits given :( => https://github.com/conwnet/github1s/issues/346
Am I alone in not jumping on the Visual Studio [Code] bandwagon? Other online editors have had "vim modes" for ages (e.g. Overleaf) and frankly I'm unlikely to write a chonking great script or project in a browser on Github -- a minor modification is much more likely. VS Code's codebase is huge. Will Github allow people to use other $EDITORs?
(Yes, I'm aware this makes me sound like an old man!)
(Yes, I'm aware this makes me sound like an old man!)
If you don't want to tie in with GitHub, there is also a vscode browser version called "code server"
https://github.com/cdr/code-server
I've been using it for the last couple of weeks on a development VPS and really love it. I'm considering moving my dev environment over to the server and just open a browser to do all the work.
https://github.com/cdr/code-server
I've been using it for the last couple of weeks on a development VPS and really love it. I'm considering moving my dev environment over to the server and just open a browser to do all the work.
GitLab had a Web IDE since Jan 2018 and we're considering adding the same . shortcut for it in https://gitlab.com/gitlab-org/gitlab/-/issues/340095
I recently discovered this feature and started using it to explore repositories and it's saved me a lot of time. My use-case is pretty simple but you can definitely do a lot more with this. For those that prefer a visual example you can watch my 2 minute YouTube video[0].
Pros:
- No need to clone code base to just explore it (cmd + p to search files)
- A lot of VS code extensions are available to use out of the box: Vim, themes, syntax highlighters
- You can import your VS code's custom settings.json + keybindings.json
Cons:
- Not all keybindings work since they conflict with the browser (cmd + shift + f to search all files sometimes bugs out and makes browser full screen)
- Not all extensions are currently available
- The terminal doesn't work
[0] https://www.youtube.com/watch?v=uTTGCgQQhgw
Pros:
- No need to clone code base to just explore it (cmd + p to search files)
- A lot of VS code extensions are available to use out of the box: Vim, themes, syntax highlighters
- You can import your VS code's custom settings.json + keybindings.json
Cons:
- Not all keybindings work since they conflict with the browser (cmd + shift + f to search all files sometimes bugs out and makes browser full screen)
- Not all extensions are currently available
- The terminal doesn't work
[0] https://www.youtube.com/watch?v=uTTGCgQQhgw
Love it.
If you have a pipeline setup you can of course run code on commit.
Hell, this turns an iPad into a limited dev station. For situations where your not at your dev system you can still get some limited work done.
If you have a pipeline setup you can of course run code on commit.
Hell, this turns an iPad into a limited dev station. For situations where your not at your dev system you can still get some limited work done.
Its scary we're heading towards a situation where everything is done in a browser. Maybe Chromeos really is the future.
It looks like this is actually just the editor from Visual Studio Online unless I've missed something.
It's great, but if it were really Visual Studio Code that would be awesome and I'd be pleasantly surprised.
(The difference being that if it's just the editor it misses out on all the compiler/analysis integrations. If Github were providing Linux containers in the cloud for working on projects - essentially the SSH feature from Visual Studio Code - it would be absolutely brilliant.)
It's great, but if it were really Visual Studio Code that would be awesome and I'd be pleasantly surprised.
(The difference being that if it's just the editor it misses out on all the compiler/analysis integrations. If Github were providing Linux containers in the cloud for working on projects - essentially the SSH feature from Visual Studio Code - it would be absolutely brilliant.)
It seems we are moving to a world of magic, where developers will be alchemists, and only a handful of people will understand "physics" or "chemistry" and know what is actually going on in the cloud, serverless, fileless, functionless development.
Since google translate and google maps, I always ask myself, what is the real price for this very convenient and engaging product.
Since google translate and google maps, I always ask myself, what is the real price for this very convenient and engaging product.
Opens up some very attractive features for the developer. The amount of vendor lock-in that this will create over time is spectacular. Can we glean something of how the future of software development looks like? Thinking especially of open-source projects here.
I'm in the beta for a few months now and use it on a daily basis.
It's pretty nice to have an extra tier between "local clone/checkout" and "commit to remote repository".
I can code on my three different machines with one "remote checkout" and commit when I'm finished.
Before, I would have to pull/push every time I switched the machine.
I used Cloud9 before, but VSCode simply has the better eco-system.
The only thing that sucks is (obviously) offline work. It would be cool if I could do more locally, especially when I'm in a train.
It's pretty nice to have an extra tier between "local clone/checkout" and "commit to remote repository".
I can code on my three different machines with one "remote checkout" and commit when I'm finished.
Before, I would have to pull/push every time I switched the machine.
I used Cloud9 before, but VSCode simply has the better eco-system.
The only thing that sucks is (obviously) offline work. It would be cool if I could do more locally, especially when I'm in a train.
You can open any GitHub repository in the web-based editor in the following ways:
- Pressing the dot ( . ) key while browsing any repository on GitHub.
- Change the URL from "github.com" to "github.dev".
rad
- Pressing the dot ( . ) key while browsing any repository on GitHub.
- Change the URL from "github.com" to "github.dev".
rad
Brave users out there, something in the security model is preventing from loading the Service Worker. I tried to relax the permissions on the domains but it's still being blocked somehow:
> Error loading webview: Error: Could not register service workers: NotSupportedError: Failed to register a ServiceWorker for scope ('https://a47e99b4-9517-4e50-87ca-95e06da14aed.vscode-webview....') with script ('https://a47e99b4-9517-4e50-87ca-95e06da14aed.vscode-webview....'): The user denied permission to use Service Worker..
> Error loading webview: Error: Could not register service workers: NotSupportedError: Failed to register a ServiceWorker for scope ('https://a47e99b4-9517-4e50-87ca-95e06da14aed.vscode-webview....') with script ('https://a47e99b4-9517-4e50-87ca-95e06da14aed.vscode-webview....'): The user denied permission to use Service Worker..
This is amazing.
However, the lack of language servers hardly make it a replacement for a desktop install of VSCode.
Writing Rust code without RLS, or Zig code without ZLS is not a great experience.
However, the lack of language servers hardly make it a replacement for a desktop install of VSCode.
Writing Rust code without RLS, or Zig code without ZLS is not a great experience.
So if VS Code can run as a web-based editor like this, what's the major difference between VS Code and Eclipse Theia (derived from VSCode)?
I thought it was amazing when someone showed me 4 years ago that you can access RStudio feature complete in a browser. Data and compute lives air gapped on the server and the developers device is just a thin client.
Great to see other development tool picking up the same usecase.
Great to see other development tool picking up the same usecase.
GitHub sure is focused on getting people to edit projects from the web, but they continue to let the actual code review part languish. It’s barely usable for any kind of serious review, and it barely even loads for large PRs.
I wonder if this results in some amount of lower quality pull requests since the "barrier to entry" is now pretty low. On the other hand, it might open up more people that can help with documentation bugs and similar.
So much discussion about this already barely a month ago:
https://news.ycombinator.com/item?id=28143722
https://news.ycombinator.com/item?id=28157661
https://news.ycombinator.com/item?id=28144833
https://news.ycombinator.com/item?id=28143722
https://news.ycombinator.com/item?id=28157661
https://news.ycombinator.com/item?id=28144833
As someone who uses git from the command line, I am finding the web-based editor extremely unintuitive and difficult to use for common git operations.
Convenient, but also, be wary to the extent that this might be steps toward the "Microsoft controls all the code" ecosystem.
If folks are curious about the kind of use cases this enables, I wrote a quick article last week that highlights some of the things that are currently possible (e.g. codebase walkthroughs, web playgrounds, knowledge-base management): http://aka.ms/githubdev-fun
The onboarding experience was odd.
I pressed "next section" thinking it would move me down to the next item in the menu, but it skipped me to another page. Then I tried to press some kind of "back" button and it ended the onboarding completely. And there doesn't seem to be a way to get it back again.
I pressed "next section" thinking it would move me down to the next item in the menu, but it skipped me to another page. Then I tried to press some kind of "back" button and it ended the onboarding completely. And there doesn't seem to be a way to get it back again.
I was trying to access [vscode](https://vscode.dev), but couldn't login using my `live.in` email address.
It says that "'live.com' does not exist in tenant 'Microsoft'", LOL
Maybe I am just dumb, but the terminal is not working for me. How do I run commands in this?
It's surprisingly good! Same experience as using VSCode on my computer. I'll definitely start using it for quick edits, then probably end using it for normal development.
Curious to see how the developing experience will evolve in the next few years.
Curious to see how the developing experience will evolve in the next few years.
I have been using my own ver. Of online vscode for about a year now, had it set up on a micro server on GCP, it has its benefits while on the run and needing a quick go-to solution , very nice of GitHub implementing this solution , handy
So cool! How did I miss this?! I’ve been looking for something like this for a while now. Github has been coming out some really great features but sometimes you have no idea they are even available.
Finally. I've been waiting for this since 2009 when the Bespin project emerged. But now I'm afraid they will occasionally deprecate the offline VSCode or make it a paid option.
- Just exploring some code.
- Quickly pull up as reference code w/ decent navigation without having to checkout locally or navigate forward/back in the source tree in GitHub.
- When reviewing PRs and wanting to check out some surrounding code that is not part of the actual PR.
- If you want to quickly commit something really small and trivial in master/a branch/a PR without having to do the whole stash/checkout/pull/change/commit/push rigmarole (like if you're in the middle of doing something else).
Things that are very annoying:
- Some of the most used VSCode hotkeys are browser hotkeys, like Ctrl+T, Ctrl+P, Ctrl+Shift+P etc. The functions aren't even rebound to anything else, they're just not available via hotkeys.
- Some extensions are not available, especially ones that (partially) may rely on some kind of local binary. I understand that, but that also sometimes rules out extensions that could partially work. Example: none of the Zig extensions work because they reference tooling binaries, so I can't even get syntax highlighting of Zig code. You could argue that's an extension packaging issue, however. That's fair.
- The PR reviewing UI needs a lot of work, because right now it's not as good as the normal GitHub UI, so currently, for larger PRs, I need to have both UIs open.
I hope in the future you can save a gist or something with custom settings/hotkeys/extensions to load. I'm sure they're working on something like that.
Update: Oh, there actually is some form of settings sync. Have to check that out.