I just tried it, and it was outright terrible.

It completely loses context when you ask for a follow up, which is kinda one of the things that made the first LLMs so impressive. My original question was about C#, when I asked for a way to do this without using a library it gave me some nonsense about Python. I tried it a second time asking it how to define string literals in C#, I asked then for array literals in the follow up chat and I get back Javascript.

It links to SO posts inline, but uses essentially random text for it, which results in links that no sane person would write. This is part of a response I got from it:

"If you want to define a connection string as string literal in your C# code, you need to either duplicate the backslash: string connection = "Data source=.\myserver;Initial Catalog=myDataBase;User ID=sa;Password=myPass" or you need to use a "here string" (the leading @) - then a single backslash will do: string connection = @"Data source=.\myserver;Initial Catalog=myDataBase;User ID=sa;Password=myPass"." This illustrates how using the @ modifier simplifies the definition of strings that contain backslashes, making your code cleaner and easier to read.

And in general usability, the lack of history is almost a dealbreaker. And I know it's not for privacy as you save all input anyway.

The "Import chat" modal also can't be dismissed if something in the background goes wrong, no idea what, but it just hangs in that case.

I just tried it, and it was outright terrible.

It completely loses context when you ask for a follow up, which is kinda one of the things that made the first LLMs so impressive. My original question was about C#, when I asked for a way to do this without using a library it gave me some nonsense about Python. I tried it a second time asking it how to define string literals in C#, I asked then for array literals in the follow up chat and I get back Javascript.

It links to SO posts inline, but uses essentially random text for it, which results in links that no sane person would write. This is part of a response I got from it:

"If you want to define a connection string as string literal in your C# code, you need to either duplicate the backslash: string connection = "Data source=.\myserver;Initial Catalog=myDataBase;User ID=sa;Password=myPass" or you need to use a "here string" (the leading @) - then a single backslash will do: string connection = @"Data source=.\myserver;Initial Catalog=myDataBase;User ID=sa;Password=myPass"." This illustrates how using the @ modifier simplifies the definition of strings that contain backslashes, making your code cleaner and easier to read.

And in general usability, the lack of history is almost a dealbreaker. And I know it's not for privacy as you save all input anyway.

The "Import chat" modal also can't be dismissed if something in the background goes wrong, no idea what, but it just hangs in that case.

It forces a "Quick Answer", "Explanation", "Tips/Alternatives" structure on answers that makes no sense at all in many cases.

I just tried it, and it was outright terrible.

It completely loses context when you ask for a follow up, which is kinda one of the things that made the first LLMs so impressive. My original question was about C#, when I asked for a way to do this without using a library it gave me some nonsense about Python. I tried it a second time asking it how to define string literals in C#, I asked then for array literals in the follow up chat and I get back Javascript.

It links to SO posts inline, but uses essentially random text for it, which results in links that no sane person would write. This is part of a response I got from it:

"If you want to define a connection string as string literal in your C# code, you need to either duplicate the backslash: string connection = "Data source=.\myserver;Initial Catalog=myDataBase;User ID=sa;Password=myPass" or you need to use a "here string" (the leading @) - then a single backslash will do: string connection = @"Data source=.\myserver;Initial Catalog=myDataBase;User ID=sa;Password=myPass"." This illustrates how using the @ modifier simplifies the definition of strings that contain backslashes, making your code cleaner and easier to read.

And in general usability, the lack of history is almost a dealbreaker. And I know it's not for privacy as you save all input anyway.

I just tried it, and it was outright terrible.

It completely loses context when you ask for a follow up, which is kinda one of the things that made the first LLMs so impressive. My original question was about C#, when I asked for a way to do this without using a library it gave me some nonsense about Python. I tried it a second time asking it how to define string literals in C#, I asked then for array literals in the follow up chat and I get back Javascript.

It links to SO posts inline, but uses essentially random text for it, which results in links that no sane person would write. This is part of a response I got from it:

"If you want to define a connection string as string literal in your C# code, you need to either duplicate the backslash: string connection = "Data source=.\myserver;Initial Catalog=myDataBase;User ID=sa;Password=myPass" or you need to use a "here string" (the leading @) - then a single backslash will do: string connection = @"Data source=.\myserver;Initial Catalog=myDataBase;User ID=sa;Password=myPass"." This illustrates how using the @ modifier simplifies the definition of strings that contain backslashes, making your code cleaner and easier to read.

And in general usability, the lack of history is almost a dealbreaker. And I know it's not for privacy as you save all input anyway.

The "Import chat" modal also can't be dismissed if something in the background goes wrong, no idea what, but it just hangs in that case.