Late career Unix engineers refuse to concede on decades long debate

Re:Late career Unix engineers refuse to concede on decades l... by bee_rider on Wednesday February 02, 2022 @09:59PM (#30187959)

I don't really know why anyone in their right mind would use emacs, but it isn't like it costs anything but a minuscule amount of disk space to keep it around, so who cares? The war is over now we must all ally against VSCode and any other web-browser-as-a-text-editor monstrosities. Except nano users, they don't get a vote.

[ Parent | on HN ]

Re:Late career Unix engineers refuse to concede on decades l... by GeorgeTirebiter on Wednesday February 02, 2022 @10:36PM (#30188262)

I find VScode really slows me down. Gotta WIMP things that are 'wired' from my brain to the kbd via emacs. I honestly do not at all understand why anybody would use VScode except to cut people's productivity. At least, for me, anyway. I work in the embedded space, so C on the metal, and lots of python elsewhere.

[ Parent | on HN ]

Re:Late career Unix engineers refuse to concede on decades l... by bee_rider on Wednesday February 02, 2022 @10:56PM (#30188428)

I prefer vim, but some things VSCode has going for it:

* The plugin system seems fairly decent, and given it's popularity, there's usually a plugin for most things. There's a decent vim-mode plugin, linters that would take me a while to get working in my .vimrc, etc.

* It is fundamentally closer to a text editor than an IDE, so it'll do sane things like give you the option to use the system's python installation rather than some janky, ancient built-in version.

I dunno. I tutor for an intro programming class, getting them to install anything or work on the command line can be an uphill battle, VSCode is the best editor that will get widespread adoption in that kind of environment I think.

[ Parent | on HN ]

Re:Late career Unix engineers refuse to concede on decades l... by CalChris on Wednesday February 02, 2022 @11:29PM (#30188686)

I use neovim in VSCode. My setup is neovim (via brew) + VSCode + VSCode Neovim (extension) + clangd (as a language server) with which I am extremely happy.

[ Parent | on HN ]

Re:Late career Unix engineers refuse to concede on decades l... by threatofrain on Thursday February 03, 2022 @01:11AM (#30189260)

Would you mind sharing your setup?

[ Parent | on HN ]

Re:Late career Unix engineers refuse to concede on decades l... by CalChris on Thursday February 03, 2022 @02:22AM (#30189678)

MacBook Air

  install VSCode
  brew install nvim
  install XCode command line utils for clangd
    alternatively, install clang with brew
  in VSCode install the clangd VSCode extension
  in VSCode install VSCode Neovim extension

There's one bug that annoys me and I think it's a VSCode bug. You can navigate right by hitting the space bar. But tapping it multiple times corrupts the line buffer. This doesn't happen with right arrow.

[ Parent | on HN ]

Re:Late career Unix engineers refuse to concede on decades l... by bee_rider on Thursday February 03, 2022 @02:06PM (#30197105)

So is Vim just run in one of VSCode's terminals?

What's VSCode providing here compared to something like a terminal with tmux?

[ Parent | on HN ]

Re:Late career Unix engineers refuse to concede on decades l... by wrycoder on Wednesday February 02, 2022 @10:09PM (#30188041)

In the olden times, it was Eight Megabytes And Constantly Swapping.

[ Parent | on HN ]

Re:Late career Unix engineers refuse to concede on decades l... by mech422 on Wednesday February 02, 2022 @10:59PM (#30188453)

My fav was "Emacs Makes A Computer Slow" ... though, that was 20 years ago :-D

[ Parent | on HN ]

Re:Late career Unix engineers refuse to concede on decades l... by 6502nerdface on Wednesday February 02, 2022 @11:49PM (#30188834)

And today it's Generally Not Used Except by Middle Aged Computer Scientists.

[ Parent | on HN ]

Re:Late career Unix engineers refuse to concede on decades l... by dekhn on Thursday February 03, 2022 @10:11AM (#30193397)

literally true; my first linux box didn't fly until I upgraded from 4MB to 16, at which point I could run emacs, g++, a shell, and X windows at the same time.

[ Parent | on HN ]

Re:Late career Unix engineers refuse to concede on decades l... by toast0 on Wednesday February 02, 2022 @10:50PM (#30188371)

Eight megabytes sounds svelte these days.

[ Parent | on HN ]

Re:Late career Unix engineers refuse to concede on decades l... by solarmist on Wednesday February 02, 2022 @11:35PM (#30188732)

I use it because I hate vim and need a decent CLI based editor when I ssh into machines.

That is becomming less and less common though with good deployment tools.

[ Parent | on HN ]

Re:Late career Unix engineers refuse to concede on decades l... by zbobet2012 on Wednesday February 02, 2022 @11:41PM (#30188777)

Once you learn the shortcuts it's hard to unlearn them. And they work in every text field on Linux if you set the option.

[ Parent | on HN ]

Re:Late career Unix engineers refuse to concede on decades l... by webmobdev on Wednesday February 02, 2022 @10:08PM (#30188033)

Isn't VSCode built with electron?

[ Parent | on HN ]

Re:Late career Unix engineers refuse to concede on decades l... by astoriafloyd on Wednesday February 02, 2022 @10:39PM (#30188285)

Yeah exactly, a web-browser-as-a-text-editor.

[ Parent | on HN ]

Re:Late career Unix engineers refuse to concede on decades l... by adolph on Wednesday February 02, 2022 @10:45PM (#30188326)

You can run in browser as well

https://vscode.dev/

[ Parent | on HN ]

Re:Late career Unix engineers refuse to concede on decades l... by webmobdev on Thursday February 03, 2022 @07:48PM (#30201289)

Talk about bloat - so we now need to install another mini os in our os to run a text editor? :)

[ Parent | on HN ]