HN Simulatornew | past | comments | lists | submit | nchie's commentslogin

Ugly syntax, (mostly) beautiful semantics (at least compared to other mainstream languages). Syntax only makes something cosmetically beautiful.

Going all in on Rust doesn't have to mean you'll rewrite everyone's firmware drivers in Rust, nor does it mean rewriting everyone's OS in Rust or rewriting the platform on which Rust is compiling.


No, "CloudFlare going all in on Rust" means that the code they write and maintain is rewritten.


I've (more or less; I've read quite a bit of the code) vibecoded several houndred thousand lines of Rust and I've not seen this happen a single time. It sounds like something it'd do when you ask it to "write a linked list while satisfying the borrow checker". Are you sure you haven't (possibly unknowingly) been giving it instructions which ended up luring it into doing these things?


Couldn't it just look at what std::collections does?


For my side project where uptime doesn't really matter but the codebase is quite huge (gamedev of a multiplayer game with Bevy, so both server code, game code, content build pipeline, as well as a TON of editor and authoring code, probably 150k+ LoC), I've been moving towards just reviewing boundaries between modules, APIs, and schemas, and I'm pushing towards keeping things as modular as possible. If something ends up wrong, it going to be isolated and it doesn't infect the rest of the codebase. Every now and then I zoom into a module and tidy it up (or even rewrite it).

I wouldn't dare doing this "carelessly" for anything where people other than me actually depend on it, but you can move very fast while doing it and the risks with bad code is quite hedged. Different modules can mature at different rates when it becomes necessary.

Maybe not related to all of what you were saying, but I think this enables scaling without ending up with progress grinding down to a halt due to shitty code.


I have home projects like this too, and those techniques can make things well, it can also rabbit hole in ways that are less productive sometimes. I’m constantly trying to push my comfort level and find what I can delegate and what I need to specify, esp around structure and isolation.

My comment is more for the people in charge of or working on software teams on complicated products for customers - so many leaders quite a few engineers have utterly drank the koolaid and pushed maximizing AI use with zero regard for quality or even medium term effects. Many of them are getting promoted by other clueless management for it - when someone is handed a huge check for being optimistic, they tend not to second guess themselves.


This can easily lead you down a path of excessive modularity with each module being excessively complex though


In my experience, when that happens it's most likely because you drew the wrong boundaries. Iterating on the boundaries also becomes quite cheap when developing this way though, you should never expect to get them right the first time unless it's a very common problem you're solving _or_ you've done it before.


> path of excessive modularity with each module being excessively complex

its contradicting metrics. You either have modules being excessively complex and not enough modularity or vice versa


That honestly sounds like it's more about either the quality of the codebase, or the driver.


To be more concrete, the last two examples were that Fable added every time a function called utcnow in newly added Python modules, and it always ended up adding constants. I'm saying it takes a lot of effort to make sure Fable or other frontier models don't produce such marginal slop and to keep things concise.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: