251–260 of 307 posts
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.
Can't one just install the rust-analyzer extension inside a codespace? It worked for me.
Earlier quoted context omitted.
> If pyright were GPL'd then MS would own their own pieces, but the contributions would be owned by others So in your hypothetical, Microsoft not only uses the GPL instead of MIT outbound, but accepts contributions under the GPL instead of the CLA it uses for most MS open source project contributions, including pyright, inbound, etc.?
Yes. If they asked for people to sign over copyright for all contributions, they simply wouldn't get many takers because it would be transparent that the only reason to ask would be to close the source later.
How is that any less true when the outbound license is MIT, and, therefore, how is the fact that they get contributions with the CLA now not a firm disproof of that claim?
I am still proud of [github1s]( https://github.com/conwnet/github1s ) No Credits given :( => https://github.com/conwnet/github1s/issues/346
Earlier quoted context omitted.
I am a developer for almost 15 years now. My primary operating system is windows. I have used Linux but only sparingly. I have used many IDEs. I have never ever felt the need to use vim. Is it fair to say, because VSCode does not have a "vim mode", it is somehow inferior as an editor? I seriously don't get it. I have used VSCode almost from day one. It is a fantastic editor and quite a capable tool. I seriously love…
I'm someone who also writes code for a living. Linux and MacOS are my primary OSes (in that order). I've used Windows, but only sparingly. I've written a lot of C, a lot of scripting languages, and a bit of C++. I've used many IDEs. For me, the "command line" workflow of Makefiles, vim & gdb are really, well, great. When I was a graduate student, I did a lot of pair-programming with a vim wizard who showed me just ho…
This one sentence convinces me that you have not used VSCode in any meaningful way.
I ditched GUI items for getting stuff done long time ago with VSCode. I just bring up the command palette and type away. Its insanely great.
Troubleshooting
If you have issues opening the web-based editor, try the following:
Make sure you are signed in to GitHub. nope
Disable any ad blockers. nope
Use a non-incognito window in your browser to open the web-based editor. nope
Earlier quoted context omitted.
I'm someone who also writes code for a living. Linux and MacOS are my primary OSes (in that order). I've used Windows, but only sparingly. I've written a lot of C, a lot of scripting languages, and a bit of C++. I've used many IDEs. For me, the "command line" workflow of Makefiles, vim & gdb are really, well, great. When I was a graduate student, I did a lot of pair-programming with a vim wizard who showed me just ho…
> VS feels like a big, bloated IDE where you have to memorise the location of 4e6 different GUI positions This one sentence convinces me that you have not used VSCode in any meaningful way. I ditched GUI items for getting stuff done long time ago with VSCode. I just bring up the command palette and type away. Its insanely great.
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
Earlier quoted context omitted.
Yes. If they asked for people to sign over copyright for all contributions, they simply wouldn't get many takers because it would be transparent that the only reason to ask would be to close the source later.
> If they asked for people to sign over copyright for all contributions, they simply wouldn't get many takers because it would be transparent that the only reason to ask would be to close the source later. How is that any less true when the outbound license is MIT, and, therefore, how is the fact that they get contributions with the CLA now not a firm disproof of that claim?
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!)
> Will Github allow people to use other $EDITORs? Yes, just clone? Most people who want other editors probably don't want browser-based ones. I'm not sure if the VSCodeVim or VSCodeNeovim extensions work on the online version yet, but I'm sure some VSCode/GitHub engineers are on the case if not. EDIT: VSCodeVim (the main "Vim" extension) does "work" on github.dev but the escape key doesn't, so as soon as you press "i…
xterm.js [1] is pretty good.
Something like gotty [2] and a engine for getting a container with a git checkout started should be relatively straight forward.