@soller

Just the other day I was barked at and blocked, in the context of the #vim "controversy"
For saying that if you insist on #Ai #vibecode free purity...
...you will be using a clay tablet for your computing needs soon.
And here we are.

I'm looking forward to a HomoSapiensLinux fork where every line of code is chiseled from a pure human bone with tools forged in artisan smithy...
...that's going to collapse in controversy because major contributors will be sprung vibecoding 😄

BTW: Any of you read that .md file before conniptions?
Would be good idea to get some human #codemonkeys to comply with the directives there 😁

@AAKL @WIRED

As a #cloudecode #vibecode user...
...it's very good with minimal fuckups.
It annoyingly slow at times and the reasoner seems to go off into the weeds sometimes
But I gave up on poking it with as stick as it gets there in the end.
But given how miserly #claude pro compute is it's concerning...
...my fix is going to be to upgrade to Claude excelsior (whatever it's called) before the next project.

@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!

#vim #neovim #AI

@JessTheUnstill Yes. One thing that I believe #ai can not change is that better programmers get the work done with fewer lines of code.

I keep hearing about #vibecode pull requests with thousands of lines of code.

That was never acceptable, before, because we already understood that lines of code carry a maintenance burden.

Suddenly we treat it like #ai will magic away the maintenance costs.

I'm seeing the increase in security breaches already, but I suspect we currently only learn about the obvious easily detected stuff.

As often happens with interesting new technology, I suspect that the costs are going to be firmly embedded in our systems before the risks are well understood by decision makers.