Comment by KolmogorovComp

5 hours ago

I don't think rust is the future anymore, despite having contributed to its compiler few times and been quite involved for years. It has spread too much and that impact compiles time too much.

I think a newer language, having the boreness of go, the compile speed and maybe comp time of zig and safety of rust will emerge, maybe with lisp syntax.

9 comments

KolmogorovComp

Reply
raincole  2 hours ago

> I don't think rust is the future

Yeah because it's the present. Rust is everywhere now.

vor_  4 hours ago

Well, that implies there's some sort of threshold that it's still reaching for and hasn't yet achieved before it can be considered successful. But it's already everywhere now. Hell, not only is it in the Linux kernel, it's even in Windows (!).

  • Gigachad  3 hours ago

    2026 has really been the year of Rust. The fact that it can run in the browser as well as natively has made it an electron killer.

Buttons840  5 hours ago

What a weird take. At first I though you were going to predict a language with an even more featureful and strict type system.

We don't need the "boreness" and human usability of Go anymore. Fast compile times are still nice though.

Lisp syntax doesn't have much value in the age of AI I think. Lisp seems optimized to make it easy to parse, and also easy to hack on the interpreter. I don't think Lisp was ever meant to optimize human readability. The uniformity and minimalism of Lisp makes it easier to learn the syntax though. -- I don't know, maybe I underestimate the value and flexibility of Lisp syntax.

I think the most valuable features of programming languages now are human readability and type systems that give guarantees humans can rely on. Some of the most exciting code AI has written has been in Lean.