Why Go and Not Rust?

Re:Why Go and Not Rust? by takeda on Monday September 16, 2019 @02:48PM (#20987280)

Yes, and that's what I'm currently doing, but it is essentially just automating writing the same code multiple times. It still has issues, like having to remember to regenerate the code on change, or making harder to use IDE features to refactor. There are also some limitations it has.

[ Parent | on HN ]

Re:Why Go and Not Rust? by nine_k on Monday September 16, 2019 @03:16PM (#20987554)

> automating writing the same code multiple times

What would you call a language that forces you to write / use a preprocessor to introduce higher-level features?

Low-level. More specifically, low-level for the domain where you're working. C is admittedly low-level because it had to be minimal even for 1970 and close to the metal. Other languages usually enjoy less drastic design constraints.

[ Parent | on HN ]

Re:Why Go and Not Rust? by pjmlp on Monday September 16, 2019 @05:05PM (#20988580)

Yep, that is why some were already using PL/I and Algol dialects almost 10 years before C came to be, alongside Fortran, Cobol and Lisp.

[ Parent | on HN ]