lemagedurage

Poor quality is the problem and since the bandwidth of editors doesn't magically grow with the amount of input, rejecting AI content is a very effective way to keep average quality up.

It's already typical to call into a native library with Python bindings for performance critical work in Python. Even Pydantic's validation runs in Rust code.

Given that the speedup is modest (~10%) and the Python 3 migration caused enough pain for users, I get it though. If it was a 2x speedup it would be a different story IMO

Their UI for viewing diffs is pretty good.

I like what they did with the website UI. I hope they can replace the text with something less AI heavy and more sincere/professional.

Looks like VSCode's editor UI on top of pi.

That's interesting. A go version to iterate on the code and a rust version to run the code might be an optimal split here.

For VSCode: 4x speedup vs TS 7, 3x vs TS 7.1

Thanks for the input, glad to hear both parties benefit.

Could you elaborate on what type of optimizations were added to TS 7.1? As in, were they more algorithmic or related to memory management?

I'm expecting IDEs to adapt to new workflows, albeit very slowly.

There is potential to build a better UI than what's constrained within a CLI's grid of characters.

You could be implicitly paid to understand what you're delivering and reading code could be a way to achieve that.

Agree.

I do feel like there's merit to having an open source implementation of anything, no matter who/what wrote it. I'm just hoping the results are validated well.

Given that you bring the weights from NVIDIA's DLSS. So basically, the repo contains reverse engineered machinery that produces the exact same output given the same model.

We're not simply changing the seed. The LLM provides some probability to tokens, and the SynthID watermarking makes it slightly more likely to choose some and slightly less likely to choose others within that distribution.