Well first off if you ask Microsoft everything is Copilot.
Secondly the confusion is designed to benefit the bull** by using ambiguous language they can do as humpty dumpty did in Alice in Wonderland and say "When I use a word, it means just what I choose it to mean. Neither more nor less"
Which benefits whatever they are pushing.
Beware those that attempt to muddle language and avoid precision in speaking.
> I often hear people use the words agent and model interchangeably
_what_ people. Would I hear one of my colleagues do this, I'll slap them across the face. With a 4 pounds salmon. Alive.
> to help us have more precise conversations.
What problem are you trying to solve. _Why_ you need more precise conversations.
I mean, I understand what you aiming at. But is it really worth it to go nitpicking at people's mental models, is the gain worth it?
Well, at least as an LLM provider you should use the right nomenclature. I just tried to sign up for Mistral. Who have Vibe (former le Chat), then they have Vibe Code, which is the same as Vibe for Code, is that like Claude Code? No, their harness is called Vibe Cli. So is Vibe Code a model? No, it is a "mode" for Vibe (the web interface). Not sure how it's different from "Chat" (the mode) but it forces you to use a project, there are no other differences it seems.
No idea what the underlying model is for any of this. More over, I don't ever vibe code, I check and understand the code that is generated by my LLMs. And yet, I use Vibe Code (the product) all day.
Lost the thread yet? I did... Tbh, it also took some time between Anthropic starting the push towards Claude Code and me understanding what is really was. Using terms interchangeably during this time of discovery is absolutely maddening. For Mistral it comes on top of their rename of services from "le Chat" and Mistral Code (still in parts of the UI) to Vibe and Vibe (for) Code.
> When you can name the layer, you can fix the layer. That is the whole point of being precise. It is not about being pedantic. It is about being able to improve things faster and more effectively.
Also, for any given fact, tons of people aren't aware. Anything you already know is news to a sizeable number of people.
Well first off if you ask Microsoft everything is Copilot.
Secondly the confusion is designed to benefit the bull** by using ambiguous language they can do as humpty dumpty did in Alice in Wonderland and say "When I use a word, it means just what I choose it to mean. Neither more nor less" Which benefits whatever they are pushing.
Beware those that attempt to muddle language and avoid precision in speaking.
On other news, water wets.
> I often hear people use the words agent and model interchangeably
_what_ people. Would I hear one of my colleagues do this, I'll slap them across the face. With a 4 pounds salmon. Alive.
> to help us have more precise conversations.
What problem are you trying to solve. _Why_ you need more precise conversations. I mean, I understand what you aiming at. But is it really worth it to go nitpicking at people's mental models, is the gain worth it?
Well, at least as an LLM provider you should use the right nomenclature. I just tried to sign up for Mistral. Who have Vibe (former le Chat), then they have Vibe Code, which is the same as Vibe for Code, is that like Claude Code? No, their harness is called Vibe Cli. So is Vibe Code a model? No, it is a "mode" for Vibe (the web interface). Not sure how it's different from "Chat" (the mode) but it forces you to use a project, there are no other differences it seems.
No idea what the underlying model is for any of this. More over, I don't ever vibe code, I check and understand the code that is generated by my LLMs. And yet, I use Vibe Code (the product) all day.
Lost the thread yet? I did... Tbh, it also took some time between Anthropic starting the push towards Claude Code and me understanding what is really was. Using terms interchangeably during this time of discovery is absolutely maddening. For Mistral it comes on top of their rename of services from "le Chat" and Mistral Code (still in parts of the UI) to Vibe and Vibe (for) Code.
Totally the wrong site to post this on. Joe, don't you see that we talk about this stuff day in day out?
From TFA:
> When you can name the layer, you can fix the layer. That is the whole point of being precise. It is not about being pedantic. It is about being able to improve things faster and more effectively.
Also, for any given fact, tons of people aren't aware. Anything you already know is news to a sizeable number of people.
Relevant xkcd: https://xkcd.com/1053/