it's really fucking annoying when the brainrot hits the maintainers of the tools you're using for more than 30 years.
-
it's really fucking annoying when the brainrot hits the maintainers of the tools you're using for more than 30 years.
-
it's really fucking annoying when the brainrot hits the maintainers of the tools you're using for more than 30 years.
i mean, i'm not again twenty, i have better things to do then to retrain fucking decades of muscle memory, and with no guarantee that the authors of the next tool won't get hit by another type of brainrot five years from now
-
i mean, i'm not again twenty, i have better things to do then to retrain fucking decades of muscle memory, and with no guarantee that the authors of the next tool won't get hit by another type of brainrot five years from now
yes, fucking vim and neovim maintainers, i'm looking at you and despair
-
yes, fucking vim and neovim maintainers, i'm looking at you and despair
@mawhrin What don't I want to know?
-
@mawhrin What don't I want to know?
@lyda that depends. do you want to know that the primary vim maintainer seems to have close enough personal relationship with claude-the-confabulation-machine (and war planner) to give it a male pronoun?
-
@mawhrin What don't I want to know?
-
@lyda that depends. do you want to know that the primary vim maintainer seems to have close enough personal relationship with claude-the-confabulation-machine (and war planner) to give it a male pronoun?
@lyda …both projects (vim and neovim) allow autoconfabulator-assisted contributions, and there's a number of conversations in vim issue tracker where it's clear everything is output of the autoplag pasted verbatim.
-
i mean, i'm not again twenty, i have better things to do then to retrain fucking decades of muscle memory, and with no guarantee that the authors of the next tool won't get hit by another type of brainrot five years from now
@mawhrin there are good muscle-memory-friendly configs for helix!
-
@mawhrin there are good muscle-memory-friendly configs for helix!
@malte unfortunately I have also incorporated in my workflow a number of plugins.
(i'm not saying i won't look, i think i'm just kind of grieving now, as irrational as it sounds.)
-
@malte unfortunately I have also incorporated in my workflow a number of plugins.
(i'm not saying i won't look, i think i'm just kind of grieving now, as irrational as it sounds.)
@mawhrin no, it's very understandable. especially with kind of old-school tools like (neo)vi(m) where a love for the craft and learning things is kind of implied the shock hits a bit harder.
-
@malte unfortunately I have also incorporated in my workflow a number of plugins.
(i'm not saying i won't look, i think i'm just kind of grieving now, as irrational as it sounds.)
-
yes, fucking vim and neovim maintainers, i'm looking at you and despair
@mawhrin yup, looks like i’m pinning at 9.0 and recompiling at major os updates.
As a fossil my requirements are minimal, and it will at least give me the chance to kill that god-forsaken command history window.
-
@malte unfortunately I have also incorporated in my workflow a number of plugins.
(i'm not saying i won't look, i think i'm just kind of grieving now, as irrational as it sounds.)
-
Time to switch to nvi.
-
Time to switch to nvi.
-
vi is basically ed with teco command structure.
-
@mawhrin there are good muscle-memory-friendly configs for helix!
-
R relay@relay.publicsquare.global shared this topic