News for hackers. Stuff that matters.
Re:What a gas stove ban means for restaurants by jdgoesmarching on Friday June 03, 2022 @06:19PM (#31614379)
I can’t imagine many professionals would wildly appreciate changing their core tool from underneath them, regardless of whether the tool is actually better.

If I wanted to stir the pot with a grenade, I’d say it’s like asking Vim users whether they should all move to VS Code.

Re:What a gas stove ban means for restaurants by pkulak on Friday June 03, 2022 @06:44PM (#31614617)
> I’d say it’s like asking Vim users whether they should all move to VS Code.

If Vim was actively contributing to climate change and fouling the air of everyone around me, I'd switch tomorrow. VS Code has Vim bindings, I'm sure. I'll be okay. We're long past the point where everybody keeps being able to do their first favorite thing at all times, _and_ we somehow also solve this huge problem we've gotten ourselves into.

Re:What a gas stove ban means for restaurants by realreality on Friday June 03, 2022 @07:33PM (#31615137)
VS Code obviously contributes more to climate change than Vim.
Re:What a gas stove ban means for restaurants by pixl97 on Friday June 03, 2022 @11:02PM (#31616549)
Yet Vim vs Emacs arguments contribute to a lot of hot air...

Zingggg

Re:What a gas stove ban means for restaurants by xigoi on Saturday June 04, 2022 @04:29PM (#31624723)
I'd gladly move to VS Code if it was more efficient than Vim (and not controlled by Micro$oft, but that's irrelevant). However, that's far from being the case.
Re:What a gas stove ban means for restaurants by rascul on Friday June 03, 2022 @06:28PM (#31614464)
Well they probably should move to emacs.

https://www.youtube.com/watch?v=lpdngXQOkBI