Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Mistral releases Devstral2 and Mistral Vibe CLI

mistral.ai

Post reply on HN
Print view View original

241–250 of 363 posts

Re: Mistral releases Devstral2 and Mistral Vibe CLI

#241

Post by bravetraveler »

Barbing wrote: post #239
bravetraveler wrote: post #213

Earlier quoted context omitted.

Oh, no . Does this policing job pay well? /s Seriously: less is more, trust the process, any number of platitudes work here. Who are you defending against? Readers, right? You wrote your thing, defended it with more of the thing. It'll permeate. Or it won't. Does it matter? You could be done, nothing is making you defend this (sorry) asinine benchmark across the internet. Not trying to (m|y)uck your yum, or whatever.…

Surprised to see snark re: what I thought was a standard practice (linking FAQs, essentially). I hadn’t seen the post. It was relevant. I just read it. Lucky Ten Thousand can read it next time even though I won’t. Simon has never seemed annoying so unlike other comments that might worry me (even “Opus made this” even though it’s cool but I’m concerned someone astroturfed), that comment would’ve never raised my eyebro…

The specific 'question' is a promise to catch training on more publicly available data, and to expect more blog links copied 'into dozens of different conversations'... Jump for joy. Stop the presses. Oops, snarky again :)

Yes, the LLM people will train on this. They will train on absolutely everything [as they have]. The comments/links prioritize engagement over awareness. My point, I suppose, if I had one is that this blogosphere can add to the chaff. I'm glad to see Simon here often/interested.

Aside: all this concern about over-fitting just reinforces my belief these things won't take the profession any time soon. Maybe the job.

Re: Mistral releases Devstral2 and Mistral Vibe CLI

#242

Post by JoshTriplett »

fastball wrote: post #49
whimsicalism wrote: post #34

Earlier quoted context omitted.

That's fine, but I don't think you should call it open source or call it MIT or even 'modified MIT.' Call it Mistral license or something along those lines

imo this is a hill people need to stop dying on. Open source means "I can see the source" to most of the world. Wishing it meant "very permissively licensed" to everyone is a lost cause. And honestly it wasn't a good hill to begin with: if what you are talking about is the license, call it "open license". The source code is out in the open, so it is "open source". This is why the purists have lost ground to practical…

And back in the day, people incorrectly called it "public domain". That was wrong too.

> if what you are talking about is the license, call it "open license".

If you want to build something proprietary, call it something else. "Open Source" is taken.

Re: Mistral releases Devstral2 and Mistral Vibe CLI

#243

Post by JoshTriplett »

fastball wrote: post #100
embedding-shape wrote: post #71

Earlier quoted context omitted.

> imo this is a hill people need to stop dying on. As someone who was born and raised on FOSS, and still mostly employed to work on FOSS, I disagree. Open source is what it is today because it's built by people with a spine who stand tall for their ideals even if it means less money, less industry recognition, lots of unglorious work and lots of other negatives. It's not purist to believe that what built open source…

You should stand up for your ideals, but dying on the hill of what you call your ideals is actually getting in the way of that. Because instead of making the point "this license isn't as permissive as it could/should be" (easy to understand), instead the point being made is "this isn't real open source", which comes across to most people as just some weird gate-keeping / No True Scotsman kinda thing.

"No True Scotsman" is about specifically about changing the rules to exclude a new example you don't want to permit. The rules haven't changed, and the attempts to violate the requirements aren't new. Proprietary licenses continue to be proprietary. Open Source continues to not allow restrictions on commercial use.

Re: Mistral releases Devstral2 and Mistral Vibe CLI

#244

Post by Havoc »

vidarh wrote: post #84
embedding-shape wrote: post #62

Earlier quoted context omitted.

Claude Code has absolutely zero features that help me review code or do anything else than vibe-coding and accept changes as they come in. We need diff-comparisons between different executions, tailored TUI for that kind of work and more. Claude Code is basically a MVP of that. Still, I do use Claude Code and Codex daily as there is nothing better out there currently. But they still feel tailored towards vibe-coding…

I really do not want those things in Claude COde - I much prefer choosing my own diff tools etc. and running them in a separate terminal. If they start stuffing too much into the TUI they'd ruin it - if you want all that stuff built in, they have the VS Code integration.

Mind elaborating a bit on the diff tool / flow you’re using? Trying to follow along better with what CC is doing

Re: Mistral releases Devstral2 and Mistral Vibe CLI

#245

Post by JoshTriplett »

fastball wrote: post #51
JimDabell wrote: post #31

Earlier quoted context omitted.

They are claiming something is open-source when it isn’t. Regardless of whether you think the deviation from open-source is a good thing or not, you should still be in favour of honesty.

*according to your definition of open-source

*according to the industry standard definition of Open Source

This kind of thing is how people try to shift the Overton window. No.

Re: Mistral releases Devstral2 and Mistral Vibe CLI

#246

Post by syntaxing »

kristianp wrote: post #206
syntaxing wrote: post #163

Extremely happy with this release, the previous Devstral was great but training it for open hands crippled the usefulness. Having their own CLI dev tool will hopefully be better

Can you explain "training it for open hands"? I can't parse the meaning.

The original Devstral was a collaboration between All Hands AI (OpenHands) and Mistral [1]. You can use it with other agents but had to transfer over the prompt. Even then, the agents still didn't work that well. I tried it in RooCline and it worked extremely poorly with the tool calls.

[1] https://openhands.dev/blog/devstral-a-new-state-of-the-art-o...

Re: Mistral releases Devstral2 and Mistral Vibe CLI

#247

Post by JoshTriplett »

fastball wrote: post #168
whimblepop wrote: post #158

Earlier quoted context omitted.

"Open-source" isn't a term that emerged organically from conversations between people. It is a term that was very deliberately coined for a specific purpose, defined into existence by an authority. It's a term of art, and its exact definition is available here: https://opensource.org/osd The term "open-source" exists for the purposes of a particular movement. If you are "for" the misuse and abuse of the term, you not…

yeahhhhhhh, that's not how this works. Unless this authority has some ownership over the term and can prevent its misuse (e.g. with lawsuits or similar), it is not actually the authority of the term, and people will continue to use it how they see fit. Indeed, I am not part of a movement (nor would I want to be) which focuses more on what words are used rather than what actions are taken.

> people will continue to use it how they see fit.

People can also say 2+2=5, and they're wrong. And people will continue to call them out on it. And we will keep doing so, because stopping lets people move the Overton window and try to get away with even more.

Re: Mistral releases Devstral2 and Mistral Vibe CLI

#248

Post by bigiain »

hadlock wrote: post #150
embedding-shape wrote: post #4

Look interesting, eager to play around with it! Devstral was a neat model when it released and one of the better ones to run locally for agentic coding. Nowadays I mostly use GPT-OSS-120b for this, so gonna be interesting to see if Devstral 2 can replace it. I'm a bit saddened by the name of the CLI tool, which to me implies the intended usage. "Vibe-coding" is a fun exercise to realize where models go wrong, but for…

>vibe-coding A surprising amount of programming is building cardboard services or apps that only need to last six months to a year and then thrown away when temporary business needs change. Execs are constantly clamoring for semi-persistent dashboards and ETL visualized data that lasts just long enough to rein in the problem and move on to the next fire. Agentic coding is good enough for cardboard services that colla…

You are right.

But there is nothing more permanent that a quickly hacked together prototype or personal productivity hack that works. There are so many Python (or Perl or Visual Basic) scripts or Excel spreadsheets - created by people who have never been "developers" - which solve in-the-trenches pain points and become indispensable in exactly the way _that_ xkcd shows.

Re: Mistral releases Devstral2 and Mistral Vibe CLI

#249

Post by dragonwriter »

kouteiheika wrote: post #96
badsectoracula wrote: post #60

Earlier quoted context omitted.

These are not permissively licensed though, the terms "permissive license" has connotations that pretty much everyone who is into FLOSS understands (same with "open source"). I do not mind having a license like that, my gripe is with using the terms "permissive" and "open source" like that because such use dilutes them. I cannot think of any reason to do that aside from trying to dilute the term (especially when some…

> I do not mind having a license like that, my gripe is with using the terms "permissive" and "open source" like that because such use dilutes them. I cannot think of any reason to do that aside from trying to dilute the term (especially when some laws, like the EU AI Act, are less restrictive when it comes to open source AIs specifically). Good. In this case, let it be diluted! These extra "restrictions" don't affec…

> Good. In this case, let it be diluted! These extra "restrictions" don't affect normal people at all,

Yes, they do, and the only reason for using the term “open source” for things whose licensing terms flagrantly defy the Open Source definition is to falsely sell the idea that using the code carries the benefits that are tied to the combination of features that are in the definition and which are lost with only a subset of those features. The freedom to use the software in commercial services is particularly important to end-users that are not interested in running their own services as a guarantee against lock-in and of whatever longevity they are able to pay to have provided even if the original creator later has interests that conflict with offering the software as a commercial service.

If this deception wasn't important, there would be no incentive not to use the more honest “source available for limited uses” description.

Re: Mistral releases Devstral2 and Mistral Vibe CLI

#250

Post by bigiain »

embedding-shape wrote: post #223
true2octave wrote: post #221

Earlier quoted context omitted.

High quality code is a thing from the past What matters is high quality specifications including test cases

> High quality code is a thing from the past Says the person who will find themselves unable to change the software even in the slightest way without having to large refactors across everything at the same time. High quality code matters more than ever, would be my argument. The second you let the LLM sneak in some quick hack/patch instead of correctly solving the problem, is the second you invite it to continue doin…

I dunno...

I have a feeling this will only supercharge the long established industry practice of new devs or engineering leadership getting recruited and immediately criticising the entire existing tech stack, and pushing for (and often succeeding) a ground up rewrite in language/framework de jour. This is hilariously common in web work, particularly front end web work. I suspect there are industry sectors that're well protected from this, I doubt people writing firmware for fuel injection and engine management systems suffer too much from this, the Javascript/Nodejs/NPM scourge _probably_ hasn't hit the PowerPC or 68K embedded device programming workflow. Yet...

Post reply on HN