Live data from Hacker News

Web-based editor

docs.github.com

101–110 of 307 posts

Re: Web-based editor

#101

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!)

Old man here - not sure what VS Code has to do with age, but I would rather use it than anything else.

Does it load fast and offer the features I want? Yes. Within reason, that's all I care about. I don't know what the perfect codebase size is for you (4mb? 16kloc?), but if that matters to you I hope you get to use that product.

Re: Web-based editor

#102
post #31

Earlier quoted context omitted.

I see this happening a lot with the young engineers. Very few of them really know what's happening under the hoods.

I am pretty much sure engineers from late 70s said the same for young engineers. Same for the engineers from 80s for those in 90s. And the trend continues. I think servers becomes the new processors and the abstraction gets higher and higher. It is the nature of evolution whether you like it or not.

> I think servers becomes the new processors

Aren't we talking about "SaaS services outside of your control" here?

Re: Web-based editor

#103
Not strictly on point, but a tangential thought…

When are going to get JavaScript accelerators in hardware and OSes such that we can have a few tabs with full blown softwares like “VSCode IDE”, “Slack”, “Spotify”, “Outlook mail”, “Zoom for video calls”, “Photoshop for your photos in the cloud” and many others?

The only thing to install on your client computer being a crazy optimised web browser!

May be ChromeOS was ahead of its time.

Re: Web-based editor

#104

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!)

> Am I alone in not jumping on the Visual Studio [Code]

These are at least 3 different questions:

1) Why should I use VS Code in general?

2) Why should I use VS Code online? (the articles topic)

3) Why should I use VS?

The answers might turn out completely different.

Personally, I have for my main languages (C++ & Python) full IDE's (VS & Wing IDE). For quick Python scripts, VSCode is considered an option that I use rather often.

In what VSCode shines is - as also other commenters mentioned - his plugin eco-sytem. This has true swiss-knife traits. So I'm using it for many secondary and ad-hoc technologies:

- CMake files

- Julia

- GPS files

- JS files

- LaTeX

- JSON

- XML

- CSS

- Markdown (vanilla, asciidoc, ReST)

- remote editing

Re: Web-based editor

#105
post #38

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…

I think what you might want is GitHub Codespaces?: https://github.com/features/codespaces . Was on HN recently too.

Hmm. $0.18 per hour for 4GB of RAM is a rather steep. A c6g.large on AWS would run you less than a half of that, for the same number of CPUs and memory. A quarter if you're happy to use spot instances. Might be neat to have an OSS tool that spins up an EC2 (or Azure or GCP) instance running Code-Server[1] (VS Code running natively on the server, but presenting the UI in the browser), with a given git repo and credentials.

Admittedly, the storage costs would be higher.

[1]: https://github.com/cdr/code-server

Re: Web-based editor

#106

Earlier quoted context omitted.

Are the other $EDITORS able to run inside a web browser?

Gotta be web-based and only other major one I know of is Atom, which was originally started by GitHub and is also owned by Microsoft now. Don't know if people are still using it much though.

There was also Adobe Brackets, but it was discontinued earlier this month.

Re: Web-based editor

#107

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!)

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…

VSCode does little out of the box. You install plugins to get what you want. Including vim mode.

Re: Web-based editor

#108

Not strictly on point, but a tangential thought… When are going to get JavaScript accelerators in hardware and OSes such that we can have a few tabs with full blown softwares like “VSCode IDE”, “Slack”, “Spotify”, “Outlook mail”, “Zoom for video calls”, “Photoshop for your photos in the cloud” and many others? The only thing to install on your client computer being a crazy optimised web browser! May be ChromeOS was a…

Chrome/Chromium is kind of an own OS already.

And the direction will probably be WASM instead of Javascript. It seems like JS runtimes are not easy to optimize further.

Re: Web-based editor

#109
post #100

Earlier quoted context omitted.

Depends what I’m doing, but most day stuff is in a JetBrains product, or vscode , or sublimetext - in that order. But I did go from notepad, to eclipse, to ST, to vscode to JetBrains, so … obviously I’m trying to get into emacs now

Companies want developers to buy into editors like religion. All of them (editors) do the same, but spending money on IntelliJ is the hardest flex because it says I’m an enterprise developer look at me.

Really? I swapped to PyCharm when I was a solo dev because it had superior code insight compared to the other editors. What is enterprise about it beyond it costing money?

Re: Web-based editor

#110

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!)

For me the advantage of VSCode is in its approach and how it has differed from other products:

- VSCode Remoting is really useful. It doesn’t suffer as much from latency as SSH or display forwarding, and lets you use some local configuration when remoting. Neovim will soon have a feature like this.

- Language servers for code intelligence has greatly improved editor support for languages. Up until the introduction and adoption of LSP, which was practically an invention of VSCode, language support was significantly more hit-or-miss with most editors. Basically only IntelliJ IDEA could do similar code intelligence across many languages. Because of LSP though, more editors and more languages can participate in inline documentation, go to symbol, errors as you type, debugging, etc. for example, many people now use language servers with Vim, and you can see useful integrations for languages like Terraform/Hashicorp HCL.

- The extensions ecosystem: it isn’t necessarily the greatest ever, but it is very solid.

- Compared to many IDEs, it remains lightweight and fast to boot. Though I’m not complaining, (regular) Visual Studio and IntelliJ are too useful to ignore in some cases.

- Unification: because it’s so versatile, across OSes, across runtimes, over remoting, over Code Spaces, you can buy into the ecosystem in your projects. You can tell Code Spaces what extensions to install and what commands to run, to try to build a nice environment. You can tell desktop VS Code what extensions are recommended, add workspace configuration to help improve the workflow. Users still can use other editors, and you can still include editor information for those editors too. But, for someone who just wants a good option to edit a specific project, pushing them towards VS Code is a really safe bet.

To be clear it has some issues too:

- There is no equally useable OSS version, as the Microsoft distribution has become more dependent on services and blobs.

- It’s not as quick and responsive as something like Sublime Text or vim.

… but honestly, I think it’s just great. If I was a new programmer again and I could jump right into projects and immediately begin working on them without having to figure out the rigmarole of version control, tool chains, build system and editor config, that would be amazing. For that reason I think Code Spaces and VSCode are net goods, though I think we ought not become too dependent on the specific solution. VSCode is never going to be the perfect editor for any specific use, but I believe overall it is usually a great editor.

Post reply on HN