Hacker News Reader

Comment by Jonnax | Hacker News Reader

It's quite funny that this is a bunch of complaints that they can't keep up with rust development and that they should do things differently but ends with a plug for their book about their experience programming in rust.

I was under the impression that rust is pretty stable?

Like web browsers get updates on a fast cadence and it rarely breaks existing web pages.

View on HN

Having critiques of something, or lamenting the subject's complexity, surerly doesn't undermine your position as an expert on something? To think the converse would, I think, steer you toward bad experts.

Rust is pretty stable. The point is that the work on Rust is happening so fast it's getting impossible to keep track of releases whilst making sure that your code doesn't go obsolete.

I think people just have to learn that "not using the newest features of the language" is not a problem. I have no problem with obsolete code, where "obsolete" means just that. I have a problem with broken code. If it ain't broken, no need to fix it.

Can you share some examples of Rust code "going obsolete"?

One thing that makes these sorts of conversations tricky is that different people mean different things when they say stuff like "going obsolete." To some people, it means "this code literally doesn't work anymore," and to other people, it means "oh no the error handling library I use isn't in vogue anymore and I feel the need to re-write everything to use the latest library."

There is not a lot of the former, but there is some of the latter, and even if it's self-imposed, some people do feel that pressure.

Reply on news.ycombinator.com