Live data from Hacker News

Web-based editor

docs.github.com

141–150 of 307 posts

Re: Web-based editor

#141

Earlier quoted context omitted.

How have you avoided vim this long? What did you edit config files with? I guess maybe if you mean you just used vi instead

You can use graphical editors over SSH. I personally tend to install micro, or use nano if that's not possible.

If I just need to do a quick edit of a text file from the CLI I usually use nano, as well.

For dev. I use an graphical editor, usually VSCode these days. I used emacs at some point a long time ago.

The good thing with git and al is that there is no need to access a remote repo., and that's one of the points, so there is usually no need to edit source files remotely.

Re: Web-based editor

#142

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…

VSCode does have a vim mode. See this plugin here: https://github.com/VSCodeVim/Vim It works surprisingly well.

Indeed, they have done such an amazing work! I usually find my self using the best of Vim and VSCode at the same time.

I also enjoy the emulated plugins (vim-surround mostly).

Re: Web-based editor

#143

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…

> Is it fair to say, because VSCode does not have a "vim mode", it is somehow inferior as an editor?

Is VSCode an inferior editor compared to Vim/Neovim? Absolutely, it is. Is Vim/NeoVim an inferior IDE experience compared to VSCode despite the ongoing evangelism by NeoVim fundamentalists? Most likely, yes.

Here's an example before I start getting flak — NeoVim doesn't have stable indent visualization lines and stable and sensible code folding support. Try writing serious Markdown documentation or Python code in NeoVim and then in VSCode.

The NeoVim website also mentions that being like an IDE is not one of its goals.

I already know the responses I'm gonna get - it's open source, submit patches or shut up, it's personal taste, those features are irrelevant etc etc.

> 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 it.

You should keep using it. Don't get swayed by people proselytising Neovim.

Re: Web-based editor

#144
post #3

Earlier quoted context omitted.

Why is it scary?

I just want to add that running in the browser does not mean running in the cloud or web. I actually once worked on enterprise software that used a browser as GUI. That's not at all bad. Of course there is always room for improvement.

By a reasonable guess your app was distributed as a binary that spun up a local web server and automatically pointed the user's browser to it. That's a perfectly fine approach for some use cases, but for many others, even the server binary isn't needed.

An extremely underappreciated approach for development and distribution is targeting the browser as a sandbox for fully local applications (embodied in static files—or better: as a single file). I see lots of people making apps and throwing them up on GitHub Pages, but rarely do the developers package them up into a form that you can download from the Releases tab from the associated repo and then double click to run. At best, they'll point at the repo with instructions in the README about running npm or yarn.

(Then again, if their build processes would also target the browser's JS engine and standard browser APIs instead of NodeJS and its proprietary ones, then the entire exercise of setting up an NPM-based development environment need not exist, either. Oddly enough, people who think of themselves as JS developers and spend their days writing web apps seem to either really dislike the thought of actually using the browser, or they're so afflicted with tunnel vision that they've missed the obviousness of using the browser runtime in this way.)

Re: Web-based editor

#145
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.

I've been trying to make VSCode work like PHPStorm. I've tried a huge combination of plugins and there's no way to do it.

It doesn't even come close. It's powerful but it's definitely not the same. I would go back to NetBeans before using VSCode. There's no religion behind it, it's just that there are tools that suit my needs better than others.

Re: Web-based editor

#146

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…

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

Exactly my point. Everyone gets a customized flavour.

Everyone can use it as its meant to be, a great tool platform that has a great community of plugins and support.

Re: Web-based editor

#147
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.

Re: Web-based editor

#148
This is more than a little ironic, because if I remember correctly, Github created the open source Atom editor, which was gaining popularity until VS Code came into the picture and absolutely destroyed it.

Re: Web-based editor

#149

Earlier quoted context omitted.

VSCode is/was a neat editor, but I fear it is slowly morphing to become an overloaded mess. It was so sleek and lightweight at first it was really a pleasure to use. But performance and bugs seem to increase, even if you don't use many or any plugins at all.

I'm curious to know what sort of dev work you do with vscode, it still feels rather snappy to me with ~40 extensions, but perhaps using it for other languages is more of a problem?

I am an embedded dev that mostly writes C/ASM, but also JS/HTML for visualization, where I use VSCode mostly.

It still has decent performance and I will continue using it. I think I have my linters correctly configured so there isn't any huge background scanning of files. But I have the impression the early versions were faster.

Re: Web-based editor

#150
post #119

Earlier quoted context omitted.

Well, nobody uses to render a table because it has so much baggage that it is incredible slow (implicit calculations for width/height for every cell etc.). These super fast super browsers we have today? You can kill all of them if you render a table with around 500.000 cells. So yes, many people use divs and spans for the same functionality.

Wait, can these@ same browsers render a table made of 500,000 divs + css without crashing?

Yes, it is much more performant. They would also render it as a table, but it would be excruciatingly slow.

Problem is the bloated standard for html tables that requires many calculations. This is why any browser-excel is implemented with divs.

Post reply on HN