24
OpenAI is Ditching TypeScript to Rebuild Codex CLI with Rust (analyticsindiamag.com)
submitted 1 year ago by to c/rust@programming.dev
15 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] [S] 4 points 1 year ago (3 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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 1 year ago* (2 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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 6 points 1 year ago (1 child)

    I don't agree go is simpler to read. It is simpler to learn the syntax but the syntax is only part of what makes a language. Having learnt both, and having spent more time actually writing go I still prefer writing rust and finding it far easier to work with then go. Go has too many hidden gotchas that you need to trip up on to learn and then remember forever or else trip up on them again.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •