@nebeker Not sure how much AI is involved. It is all of these automatic blocks stuff, eg after typing “match”. Or inserting complete nonsense when hitting some ‘known’ word from a lib. And when my eyes are elsewhere, I get two lines of garbage right away
There are now, after months of push-back on the shit they were originally trying to pull.
A “plugin”
installed by default
that you couldn’t permanently disable (though that may have been a bug)
that you couldn’t uninstall (that was intentional)
had no corporate level “We can’t legally use AI so remove all possibility of it causing us legal problems please” option.
I say “plugin” because up until this , plugins were optional, could be uninstalled and generally didn’t “accidentally” re-enable themselves on restart.
They’ve fixed most of it now, but the backlash was interesting to say the least.
Though, to be fair that was only the full AI and not the built in “small” line completion, not sure what the current state of the “big” line completion is.
@nebeker Not sure how much AI is involved. It is all of these automatic blocks stuff, eg after typing “match”. Or inserting complete nonsense when hitting some ‘known’ word from a lib. And when my eyes are elsewhere, I get two lines of garbage right away
Ah, matter of preference I suppose. At least there are a lot of settings to disable that stuff.
There are now, after months of push-back on the shit they were originally trying to pull.
A “plugin”
I say “plugin” because up until this , plugins were optional, could be uninstalled and generally didn’t “accidentally” re-enable themselves on restart.
They’ve fixed most of it now, but the backlash was interesting to say the least.
Though, to be fair that was only the full AI and not the built in “small” line completion, not sure what the current state of the “big” line completion is.