What a bad idea. From the information at hand I don't see how this can go well.

I was indeed thinking this looks awfully similar to some things we've seen in the past... It needs to be fought as well.

Training sets are obviously already contaminated... now it'll be a race of hiding such mistake under the carpet with human interventions. That'll be a boon for misinformation. That's what we get for a useless large models arm race.

This browser is really an horrible data harvesting platform for Microsoft's benefit. They never learn...

Well, people asking relevant questions slow you down obviously... since the goal about the latest set of generative models is to "move them into customers hands at a very high speed" this creates tension. Instead of slowing down they seem hell bent at throwing ethics out of the window.

Don't believe too good to be true marketing claims by vendors. Clearly something went wrong there and the benchmark has been gamed.

Alright, this going to be interesting. Pass me the pop corn. It's definitely a welcome move in any case.

This is indeed a concerning move... it's not about legacy, it's about closing an ecosystem.

More elements on why we should all be concerned about Visual Studio Code and the state of development tools overall. It's clearly moving more and more proprietary. Visual Studio Code's ecosystem is a very well designed trap. I see it more and more around me (even tried it for a little while to see what it was all about). What can I say... Go Kate Go! And also we clearly need many more LSP servers.

The obvious problem with VS Code, you just cannot have any trust into it.

More details coming out about the .NET Foundation drama. This indeed looks bad and concerning regarding the stewardship of this foundation.