←back to thread

333 points steveklabnik | 2 comments | | HN request time: 0.476s | source
Show context
sleepy_keita ◴[] No.45033134[source]
I find it interesting how Rust is gaining momentum in tooling like uv and now rv.
replies(2): >>45033154 #>>45033816 #
inopinatus ◴[] No.45033816[source]
Rust is the new C. Go had a shot but went in an applications direction. I predict that very soon, perhaps even inside of three decades, Rust will become the dominant, first-choice systems programming language.
replies(4): >>45034164 #>>45034544 #>>45034814 #>>45035389 #
frollogaston ◴[] No.45035389[source]
I think Go is going away. It occupies such a weird niche. People have said it's good for app backends, but you should really have exceptions (JS, Py, Java) for that sort of thing. For systems, just use Rust or worst case C++. For CLIs, it doesn't really matter. For things where portability matters like WASM, can't use Go. Bad syntax and type system on top of it.

What if Google spent all that time and money on something from the outside instead of inventing their own language? Like, Microsoft owns npm now.

replies(3): >>45035789 #>>45037084 #>>45037982 #
1. skotobaza ◴[] No.45035789[source]
I always thought of Go as a middle ground between C and Python. From C it gets simple syntax, from Python - "batteries included" part.

Deserializing JSON and XML is a breeze from my experience. And it's available out of the box. But I guess C++ will get there with reflection having been approved in C++26.

So I don't think it will go away (in the coming years at least), since a lot of tools is written in it.

replies(1): >>45047908 #
2. frollogaston ◴[] No.45047908[source]
It's not that bad to handle some JSON in C++ or Rust. It can get annoying if you're doing it everywhere, but that's usually that's the kind of use case where JS or Python works anyway. Yes I get that some people prefer Go, but it's not necessary enough to guarantee that it'll stick around.