Did someone do a #neovim-fork before it got #SlopCode added to it?

[kkarhan@infosec.space]

Did someone do a #neovim-fork before it got #SlopCode added to it?

• Cuz I'd put that on the @OS1337 wishlist in lieu of neovim…

#OS1337 #NoAI #AntiAiAction #NoSlop #Enshittification #AI #AIslop

[reiddragon@fedi.catto.garden]

@kkarhan @OS1337 I highly doubt neovim will get a pre-slopcode fork; it has always been the kind of project to chase fads so this is just par for the course for them

[reiddragon@fedi.catto.garden]

@kkarhan @OS1337 though I have to say, I do hope Vim gets a pre-slopcode fork; surely after over 30 years of avoiding fads there's enough of a community around it that won't stand for that shit

[kkarhan@infosec.space]

@reiddragon problem is that allegedly #vim also does the same, not only #neovim.

• Maybe someone will just yeet all the #claude commits and do a nvim-ng or nouveauvim instead?
  • Cuz personally I think the ability to turn it into a real #CLI / #TUI-based #IDE with #Lua instead of #VimScript really made it nice.

Espechally with #nvChad being a nice default…
https://www.youtube.com/watch?v=c4OyfL5o7DU

#OS1337 #NoAI #AntiAiAction #NoSlop #Enshittification #AI #AIslop

[reiddragon@fedi.catto.garden]

@kkarhan Vim also fell to the slopcode now, but this is a recent thing; NeoVim started chasing fads since it forked, Vim only started recently, years after its original creator passed away and someone else had to pick up the torch. But the culture around vanilla Vim for most of its life wasn't one of chasing fads, it was one of avoiding them. I know I'm probably high on hopium pills right now but there just isn't anything else like Vim around to switch to, and even neovim just wasn't it

[kkarhan@infosec.space]

@reiddragon @OS1337 true, true…

[reiddragon@fedi.catto.garden]

@kkarhan @OS1337 nvchad is just junk

[kkarhan@infosec.space]

@reiddragon well, @mrmasterkeyboard did #fork #vim at the last pre - #vommit point of the #git...

• It's known as evi, which I think is a good name...
  • Maybe someday we get like nevi (basically neovim on #evi basis)...

Cuz I wish for that to happen, not only because I want to see a better #neovim but also because we better become more #intolerant to the #intolerable #Enshittification!

• If we don't take a hard stance against #AIslop and #vommits (aka. *"#vibeCode|d #commits) we'll end up with a #TechStack out of shit, piss, diharrea and spit that is *unsalvageable!
  • Some may think that makes me a "#Hardliner" but I'd rather have my few principles than being a #sellout!

[reiddragon@fedi.catto.garden]

@kkarhan @mrmasterkeyboard yeah, I know about it, I'm currently discussing details about the fork with NND in #evi on OFTC

[mrmasterkeyboard@mastodon.social]

@reiddragon @kkarhan imagine, we build an NEVi mode into EVi... just like :nevi?

[kkarhan@infosec.space]

@mrmasterkeyboard @reiddragon I mean, that would be cool based upon the command it's called up.

• evi: basically vim minus #AIslop.
  • Basically loads the init.vim (like #vim does) configuration file and moves on from there`
• nevi: basically neovim minus #AI #slop.
  • Loads the init.lua configuration like #neovim would.
• neville: basically something to add/remove NvChad or other preconfigs.
  • In case someone wants to switch things...

It would also make it convienient to go between "basic mode", "comfort mode" and "perdormance mode"...

• So if one "riced too hard" they don't end up with a broken editor they can't fix themselves...
  • Which is desireable for a productivity tool.
  • Propably you'd even add something like a -noconf flag to ignore all configurations and just load the blank evidefaults...

After all, people accept that with "#StallmanOS" aka. #GNUemacs too. (See org mode)...

• And #toybox does the same with it's "single binary" mode where one calls up it's vi implementation buy calling the binary and then the vi subcommand like ./toybox vi ...
  • So it would be possible to do it, but I'm shure you'll figure out that once you want to cross that bridge...

[reiddragon@fedi.catto.garden]

@kkarhan @mrmasterkeyboard that would bloat up the codebase like nothing else; also, there's already a neovim fork around.

https://github.com/icevim-editor/icevim/

Its focus seems to be more on not breaking shit because apparently Neovim likes to break stuff all the time, but rn it's probably the best there is for a slop-free neovim

[kkarhan@infosec.space]

@reiddragon @mrmasterkeyboard yeah, that makes more sense.

I definitely intent to put evi and icevim on the package wishlist for @OS1337 ...

[lemmus@social.vivaldi.net]

@kkarhan People have started making excuses for thinking using knowledge destroying tools built on theft, environmental destruction and exploitation is a bad thing. The Overton window is utterly insane on generative AI these days. “Of course I can see there are good uses of the Torment Nexus, but...” Seriously, it's a $#%#$%%#$% Torment Nexus!

[kkarhan@infosec.space]

@Lemmus precisely that!

• It's like excusing #murder because a #judge ordered it under the false pretense of #justice when in fact that doesn't undo harm caused nor does it make it less cruel by calling it "#DeathPenalty"!

[kkarhan@infosec.space]

@reiddragon @mrmasterkeyboard done!

#OS1337 #noAI #AIslop #Enshittification #deshittifiaction