Rendered at 19:36:22 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
conqrr 23 minutes ago [-]
Can someone who undertands verification systems better explain how the spec/intents are created for such usecases along LLMs? Does a human form the spec or the system generates one based on human's natural language intent?
I haven't followed this area but it seems like LLMs are used to bridge and form a hybrid spec?
fuddle 23 minutes ago [-]
Is there an open source alternative to this?
ajasmin 1 hours ago [-]
There are a lot of verification tools for rust popping up recently it's getting hard to navigate the space.
OreganoTrail 2 hours ago [-]
> Aristotle can prove that your code has no undefined behavior ... even inside unsafe blocks.
That's crazy, I haven't seen any other system that really tries to do that.
bryanlarsen 1 hours ago [-]
Some others in the Rust ecosystem, not a complete list:
Wow, this is a pretty advanced use of syllogistic logic!
5555watch 1 hours ago [-]
Maybe a hot take, but I don't think Aristotle is a good name for an AI.
expectfun 1 hours ago [-]
"Feels like in the future the only languages would be Rust and Lean"
rafram 1 hours ago [-]
Rust is a terrible language for many of the tasks people try to shoehorn it into. As processors and memory get faster, garbage collection only becomes more attractive, while the borrow checker remains a PITA that gets in the way of plenty of sensible architectures. In a sane world, Rust will never take over frontend development, for example - it’s a terrible fit.
(I qualify with “in a sane world” because obviously it could happen. In a truly sane world, JavaScript would never have happened, either!)
ChadNauseam 3 minutes ago [-]
As processors and memory get faster, people will expect more from them. And the fact that languages like Rust give you fine-grained control over memory allocation is part of what allows it to be so performant on modern hardware where memory latency is still relatively high and bandwidth still relatively low. My intuition is that any data-intensive operation (such as blurring an image) will almost always be far faster in rust than javascript.
afavour 34 minutes ago [-]
> As processors and memory get faster, garbage collection only becomes more attractive, while the borrow checker remains a PITA that gets in the way of plenty of sensible architectures.
I’d counter with: as LLM driven coding becomes more and more common the PITA borrow checker is something individual developers interact with less than less. Garbage collection looks more and more like a waste when an LLM can examine memory allocations before the app is even built.
rafram 9 minutes ago [-]
Maybe, but whatever workarounds or compromises the LLM has to settle on to satisfy the borrow checker will live in the code forever, while garbage collection can continue to get faster in the same executable.
weinzierl 26 minutes ago [-]
> As processors and memory get faster, garbage collection only becomes more attractive
Just because they did in the past doesn't mean they will continue to do so in the future. If we are honest then Moore's Law ended a decade ago (the latest) and we've been picking the low hanging fruit we left alone during Moore's era since. This too will come to an end for sure, just not a pretty and well defined one.
So, my conclusion is the opposite. Garbage collected and DX optimized languages made sense while processors and memory got faster, the future will be elsewhere.
rafram 12 minutes ago [-]
Did Moore’s Law really end? My ARM Mac from five years ago is a literal order of magnitude faster than a gigantic, beefy desktop tower from five years before that, and my newest ARM Mac from this year is another 5x or so faster than my first. Computers continue to get much, much faster, at least in terms of time to completion of normal workloads.
expectfun 53 minutes ago [-]
I'm not advocating for Rust (or against it), I'm just stating that currently it's hard to open the news without seeing Rust expanding somewhere, and it feels like "taking over the world". Whether that is bad or good is another question.
And yeah, it feels a bit like JavaScript a while ago, that's a good comparison.
teiferer 44 minutes ago [-]
> In a truly sane world, JavaScript would never have happened, either!
Out of curiosity, what do you envision would have taken its place in frontend, in that sane world? (Honest question, no bad faith agenda.)
rafram 16 minutes ago [-]
No language that perfectly fills that niche exists, because none was ever needed. JavaScript eventually became Good Enough. Python is OK, but it’s an old language at this point and it suffers a lot of technical debt.
JavaScript’s biggest weakness IMO is its absolutely abysmal standard library, particularly in terms of data structures. (At least we have Map and Set now, but still no way to define a hash/equality function for a type…) The situation is so bad that essentially any other modern programming language would be an improvement.
irishcoffee 22 minutes ago [-]
I for one wish python had taken the spot JavaScript holds.
That's crazy, I haven't seen any other system that really tries to do that.
- cargo-anneal - VeriFast - RefinedRust - safety-tags - Verus
These 5 use very different mechanisms. This is still a very active research area.
https://github.com/google/rust-skills/blob/main/unsafe_rust_...
(I qualify with “in a sane world” because obviously it could happen. In a truly sane world, JavaScript would never have happened, either!)
I’d counter with: as LLM driven coding becomes more and more common the PITA borrow checker is something individual developers interact with less than less. Garbage collection looks more and more like a waste when an LLM can examine memory allocations before the app is even built.
Just because they did in the past doesn't mean they will continue to do so in the future. If we are honest then Moore's Law ended a decade ago (the latest) and we've been picking the low hanging fruit we left alone during Moore's era since. This too will come to an end for sure, just not a pretty and well defined one.
So, my conclusion is the opposite. Garbage collected and DX optimized languages made sense while processors and memory got faster, the future will be elsewhere.
And yeah, it feels a bit like JavaScript a while ago, that's a good comparison.
Out of curiosity, what do you envision would have taken its place in frontend, in that sane world? (Honest question, no bad faith agenda.)
JavaScript’s biggest weakness IMO is its absolutely abysmal standard library, particularly in terms of data structures. (At least we have Map and Set now, but still no way to define a hash/equality function for a type…) The situation is so bad that essentially any other modern programming language would be an improvement.