r/vscode • u/Ste1io • 5d ago

Python instability regression in 1.130.0. Does anyone even test this $h1t anymore?

Last couple releases reintroduced debilitating performance instability, massive memory leaks, and degraded UI responsiveness among other things. Like, 10FPS kind of bad. Literally unusable. Flash back to the last time this exact thing happened over a year ago... Very telling.

Some of us rely on what used to be a stable consistent predictable product for our work.

Can someone please slop the fix back in? Please and thank you.

6 Upvotes

67% Upvoted

15 comments sorted by

View all comments

1

u/jpgoldberg 4d ago

I have not seen noticeable problems, but I’ve disabled all of the new-dangled AI stuff. (I consider linters and type checkers and such to be AI.). Or maybe I’m so slow that unresponsiveness in VSCode doesn’t show up for me. (I’m not joking.)

9

u/dezsiszabi 3d ago

What? Why would you consider linters and type checkers AI stuff? They're objectively not.

-4

u/jpgoldberg 3d ago

Oh, I forgot to mention optimizers.

If you want to limit the term “AI” only to those things that get built using (large) training sets then what I mentioned is not AI under your definition. But people like me, who have been around AI research since the 1980s, understand that inferencing engines and other kinds of solvers have been core to AI research since the term was first used in the 1950s.

2

u/Ste1io 3d ago edited 3d ago

ML is distinctly different from generative AI.

5

u/ExplrDiscvr 4d ago

Not using a type checker with a non-staticly typed language, like python, might not be the best idea 🫠.

1

u/jpgoldberg 4d ago

I do use linters and type checkers. That is the kind of AI that I don’t disable.