barrell
Joined 4 years ago
Joined 4 years ago
If they don’t end up switching models by the end of the year, I think that says a lot about the models. If they’re just waiting for an appropriately large or small model, or waiting to get large 4 put through its paces before switching, I think that’s a pretty ego-less way to go about it, and could speak pretty highly in a way.
Mistral large 3/medium 3.5/small 4 have all been pretty dated for a while so if they just needed a stopgap, I could understand. Now that large 4 is out though, we will see if that was the case.
I prefer using a European provider though so this is actually cheaper than I can find elsewhere.
Turns out they’re using GLM in le chat. Quite concerning if I’m being honest, and this is coming from a huge mistral fanboy.
I wish we could toggle mistral large 4 in le chat so I could get a feel for it.
Too many models now to remember specifics - I believe deepseek v4 did this and one of the gpt models (5? 5.1? 6?) did this if I recall correctly. I’m also fairly confident Google has had a few promotional periods on launch of the model, I seem to remember them starting the trend.
This is just my headcanon though.
Mistral models were the best for my use case when they came out, but they’re mostly almost a year old now. Hard to keep justifying using them, especially with all the price cuts this year on other models.
Many comments, but I'm surprised no one has mentioned the ease and quickness LLMs have to advise you to leave relationships. Doesn't matter the context, how little you tell them, or how close the person is, an LLM is always ready to drop them at the tip of a hat.
It's weird enough chatbots try to be your friend. Doubly weird that the search engine tries to be your friend. The downright dystopian part is how often they tell you to leave your real friends.
I’ve spent the last three years tweaking away at this algorithm. There are so many little details that have had to come together to make it an enjoyable experience. For example, take the one problem of balancing multiple language: What is the best way to balance multiple languages? How should you switch between them, and how often? What happens if you are over performing in one language and underperforming in another? What happens if you have more reviews in one language than another that isn’t in line with your priorities? How do you deal with competing learning speeds and language priorities? Spiky review burdens? What happens when you change your language priorities?
This is probably the most trivial part of the algorithm, and it took years of trial and error and dozens of iterations to get it to feel right. It requires knowing about SRS, the FSRS algorithm, language learning principles, and even then tons of experimentation, trial and error, and hundreds of days of daily usage.
I’ve asked LLMs every step of the way what to do. I’ve probably taken <1% of the advice I was given. Just asking an LLM “build an SRS app that balances multiple languages” would produce a result, but one that would definitely be terrible to use, and probably would end up slowing you down, not speeding you up. Explaining to it any of the issues that you would come across when using it will likely suggest to changes that will only make things worse, based on the thousands of terrible ideas I’ve seen confidently produced.
The hard part of a product is not the idea, but the experience of using it. The valueable work is normally not in the big feature specs, but the hundreds of little paper cuts that have all been smoothed over. The time saved is not because you don’t have to code it, but is from not having to become an expert in several different fields.
I would not want that in my product.
For example from the original analogy, if you told an entrepreneur that because they didn’t use AI, they were not an entrepreneur, but instead “unskilled” or a “beginner”, that would be disparaging; pejorative.