On the one hand, I love Rust, love seeing Rust winning, on the other hand: the cynical part of me observes this as a way for them to say it's safer to use, somehow. In the sense that people fling Rust around in a kind of showey way.

Already we've been seeing projects fuck up with isolation irt MCP servers, so this is the backdrop to observe this kind of change.

I know this is blasphemy, but why not Go? Why Rust? I love writing Rust CLIs, but somehow I feel the personal arguments I make for such things don't really hold up in industrial settings like this (in particular, a small open-source CLI project that interacts with networking).

There's nothing wrong with using Rust here (Rust is great for business logic!), but the choice here almost makes me suspicious of the motivations.

Also there's existing Rust solutions in this area! Namely: https://github.com/sigoden/aichat

I don't really enjoy using AI when coding, but aspirationally, I'd rather support other projects than OpenAI, who is only a nonprofit in concept and is actively attempting to become a for-profit, whilst behaving like a VC funded startup.

(Not to mention the fact that mainline models are explicitly developed with the intention of destroying labor, in general)

[–] SorteKanin@feddit.dk 3 points 1 week ago (5 children)

I think I read somewhere that part of the motivation is that they won't need a runtime to be installed to use it, but Go could fill that role as well of course.

But I think you said it yourself:

I know this is blasphemy, but why not Go? Why Rust? I love writing Rust CLIs

I guess they also prefer Rust to Go. I'd choose Rust over go for a CLI any day. Why do you say Rust wouldn't be good in an "industrial setting"? I use Rust professionally and I don't see any problems in that setting.

[–] solardirus@slrpnk.net 1 points 1 week ago* (last edited 1 week ago) (4 children)

Go is a simpler-to-read language that does not involve lifetimes (as you know, it is GC'd). For a lot of smaller projects like this, the boringness of Go is preferred. Less mental bandwidth required.

I'll admit my definition of "industrial" here was vague, but I think you can get my point. I'm not trying to say that Rust isn't good in a business setting - my job also has Rust in the code!

However, for these purposes, most of the benefits of Rust in this situation are already provided by Go.

[–] pitbuster@lile.cl 2 points 1 week ago

@solardirus I find the situation to be the opposite, you need more mental bandwidth to navigate a go codebase. The signal to noise ratio is very poor because of badly designed error handling, poor libraries at some domains and lack of some modern goodies on programming languages making you having to reinvent the wheel every time.

Also, you rarely have to explicitly specify lifetimes.

@SorteKanin

load more comments (3 replies)

load more comments (8 replies)