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

Learnings from 100K lines of Rust with AI (2025)

zfhuang99.github.io

Post reply on HN
Print view View original

201–210 of 225 posts

Re: Learnings from 100K lines of Rust with AI (2025)

#201

Post by beepbooptheory »

embedding-shape wrote: post #195
keeganpoppen wrote: post #177

Earlier quoted context omitted.

i legitimately cannot divine what you are saying at all with this. there are so many dangling antecedents and modifiers that it is completely impossible. and i say this out of a genuine desire to understand what your argument is, knowing full well that i likely disagree with it.

Alright, let me explain, hopefully simpler: GP made told us their experience with working with LLMs, and some pointers to what they found to be working. The comment I replied to just says "This is astrology for devs" which basically is a cheap putdown without any reasoning nor arguments for why the commentator believes so. My comment is urging them to actually participate in the discussion, not just post their soundb…

https://news.ycombinator.com/newsguidelines.html

> Please don't post comments saying that HN is turning into Reddit. It's a semi-noob illusion, as old as the hills

Re: Learnings from 100K lines of Rust with AI (2025)

#202

Post by [deleted] »

munksbeer wrote: post #199
keeganpoppen wrote: post #177

Earlier quoted context omitted.

i legitimately cannot divine what you are saying at all with this. there are so many dangling antecedents and modifiers that it is completely impossible. and i say this out of a genuine desire to understand what your argument is, knowing full well that i likely disagree with it.

You can't be serious. It couldn't be more obvious what the poster was referring to, a drive by put-down comment with no attempt to discuss anything seriously is more highly upvoted than an objection to such a comment. What is this place for? Dang tells us, curious discussion. The guidelines explicitly state that certain comments are not in the spirit. But the community seems to have decided otherwise, which is a sham…

[deleted]

Re: Learnings from 100K lines of Rust with AI (2025)

#203

Post by pelasaco »

flossly wrote: post #193
pelasaco wrote: post #46

Earlier quoted context omitted.

If I was forced to write it myself, i would love to keep writing ruby. What a wonderful language. I dont write ruby anymore, mostly using golang and python.. but ruby still a joy.

Have you looked at Kotlin? I looooved Ruby. But now I've come to a conclusion that a stronger type system is worth it: in teams, for LLMs, for my own sanity. Kotlin is basically a Ruby (OO first with lots of FP goodness) with a serious type system. And where Ruby uses C-written libs in some places, with Kotlin one uses Java written libs from time to time. See http4k for a nice implementation of Rack + a lot of goodne…

> Have you looked at Kotlin?

Yes Kotlin is nice too. Type systems are important and helpful. Performance is a must too.. that's why we all in some point left ruby... but ruby makes you happy.. Maybe because my experience with Kotlin is restricted to Android, i didnt love that that much. Same with Crystal or even JRuby.. it's almost ruby, but not really.

Re: Learnings from 100K lines of Rust with AI (2025)

#204

Post by satvikpendem »

beepbooptheory wrote: post #201
embedding-shape wrote: post #195

Earlier quoted context omitted.

Alright, let me explain, hopefully simpler: GP made told us their experience with working with LLMs, and some pointers to what they found to be working. The comment I replied to just says "This is astrology for devs" which basically is a cheap putdown without any reasoning nor arguments for why the commentator believes so. My comment is urging them to actually participate in the discussion, not just post their soundb…

https://news.ycombinator.com/newsguidelines.html > Please don't post comments saying that HN is turning into Reddit. It's a semi-noob illusion, as old as the hills

Indeed, with the corollary of, please don't write Reddit-tier comments on HN either, then one wouldn't have to say it's turning into Reddit.

Re: Learnings from 100K lines of Rust with AI (2025)

#205

Post by andai »

raincole wrote: post #188
knivets wrote: post #103

Earlier quoted context omitted.

This is astrology for devs.

People though asking LLM to output the reasoning steps was astrology until it's standardized and made ubiquitous.

Didn't multiple studies find the reasoning traces didn't have much to do with the final output? And even that outputting placeholder tokens during reasoning has a similar beneficial effect on benchmark scores?

(I don't think that's the full picture but, there's definitely something fishy going on there.)

Re: Learnings from 100K lines of Rust with AI (2025)

#206

Post by dmm »

boitiga wrote: post #30
jdw64 wrote: post #9

I'm also shifting to an vibe coding workflow, but I have a genuine question: whenever I use AI for Rust, it makes an insane amount of lifetime errors. I have no idea how people are churning out so many lines of code so quickly. Honestly, despite all the hype around Rust in the community, the fact that AI can't handle lifetimes reliably makes me reluctant to use it. The AI constantly defaults to spamming .clone() or w…

Honestly Rust is an UGLY language. For whatever powers it possesses in memory safety, its cryptic symbology is reminiscent of assembly. This is a problem when language designers are mathematicians and don’t understand typographical nuance and visual weights.

What aspects of Rust do you find ugly? Can you provide three examples?

Re: Learnings from 100K lines of Rust with AI (2025)

#207

Post by embedding-shape »

beepbooptheory wrote: post #201
embedding-shape wrote: post #195

Earlier quoted context omitted.

Alright, let me explain, hopefully simpler: GP made told us their experience with working with LLMs, and some pointers to what they found to be working. The comment I replied to just says "This is astrology for devs" which basically is a cheap putdown without any reasoning nor arguments for why the commentator believes so. My comment is urging them to actually participate in the discussion, not just post their soundb…

https://news.ycombinator.com/newsguidelines.html > Please don't post comments saying that HN is turning into Reddit. It's a semi-noob illusion, as old as the hills

Awesome, you did understand the reference I made, I was afraid I was too sneaky about it but seems it was just clear enough :)

Re: Learnings from 100K lines of Rust with AI (2025)

#208

Post by beepbooptheory »

embedding-shape wrote: post #207
beepbooptheory wrote: post #201

Earlier quoted context omitted.

https://news.ycombinator.com/newsguidelines.html > Please don't post comments saying that HN is turning into Reddit. It's a semi-noob illusion, as old as the hills

Awesome, you did understand the reference I made, I was afraid I was too sneaky about it but seems it was just clear enough :)

Of course! That point in the guidelines has links to some prior art in this vein. Highly recommend it for you.

And please, do better next time!

Re: Learnings from 100K lines of Rust with AI (2025)

#209

Post by beepbooptheory »

satvikpendem wrote: post #204
beepbooptheory wrote: post #201

Earlier quoted context omitted.

https://news.ycombinator.com/newsguidelines.html > Please don't post comments saying that HN is turning into Reddit. It's a semi-noob illusion, as old as the hills

Indeed, with the corollary of, please don't write Reddit-tier comments on HN either, then one wouldn't have to say it's turning into Reddit.

Two wrongs don't make a right, as they teach us as children.

Re: Learnings from 100K lines of Rust with AI (2025)

#210

Post by hollerith »

pjmlp wrote: post #151
rirze wrote: post #56

Earlier quoted context omitted.

Then your domain problem you’re trying to solve doesn’t benefit from Rust. Sounds like your work doesn’t need Rust and that’s ok. But don’t generalize.

Unless you're writing kernels, or high integrity systems with memory allocation constrains there is very little reason to use a language like Rust. Everything that people find great on Rust with exception of the borrow checker, can be found in any compiled language from ML linage. And even that is fading away as they introduce a mix of linear types, dependent types, effects and formal logic.

Rust has uses you haven't mentioned. For example, each compiled language from the ML lineage (and almost every language period) has its own runtime, particularly, its own assumptions and contracts about heap-allocated storage. In contrast, Rust famously does not need a runtime library -- and it is low-level enough that it can usually (with enough cognitive effort by programmers) interface with an arbitrary foreign runtime library -- so when the goal of the code to be written is to interface with code in a compiled language from the ML lineage, you usually have only 2 memory-safe options, namely, the same language as the code-to-be-interfaced-with and Rust.

The situation is a little more complicated than what I just wrote because two programs written in different ML-style languages could communicate via inter-process communication. But I don't see that. (Maybe my experience is not broad enough?) What I see is, e.g., Python libraries written in C and C++ (and Fortran, which is also not memory-safe) for performance reasons where the only memory-safe language that could have been used instead is Rust.

Post reply on HN