logoalt Hacker News

We Should Be Able to Change Our Languages

21 points • by surprisetalk • last Friday at 1:00 PM • 10 comments • view on HN

Comments

brinepot • today at 4:28 AM

Moving from Java to Kotlin was a breath of fresh air; sometimes a language change genuinely unlocks productivity.

pie_flavor • today at 3:58 AM

Rust has been a practical experiment in macros for ten years now. I think it is safe to say the results are in: macros are great, and you just needed to have a better style of macros. Making and using something like `tokio::select!` in C-style macros is miserable, but `tokio::select!` is easy to use and understand in Rust.

tombert • today at 3:27 AM

At the risk of being a bit of a douchebag, it seems like nearly every tech opinion piece I read now boils down to "things used to be hard but they aren't anymore because LLMs can understand things faster than we can, so can ignore/change fundamentals!"

I didn't really find the argument convincing the first time and I don't really find it convincing now.

That said, with regards to macros, I actually do agree that the fear against them is broadly overblown. I have seen scary terrible horrifying macro soup in Clojure, but that has generally been outlier cases. Something like core.async abuses the hell out of macros, and despite that I think it very often increases readability and understanding of the language.

➕ show 2 replies
tinlid • today at 3:56 AM

My last project needed Rust for one module, but the rest was Go. Felt silly rewriting core logic just to stay unified.

crate_88 • today at 4:26 AM

[dead]