Things you can’t do in Rust (and what to do instead)

Re:Things you can’t do in Rust (and what to do instead) by ta_ca on Saturday May 15, 2021 @09:20AM (#27164949)

didn't lisp prove the opposite? you can go lower than c and higher than any language we currently have in the same language?

[ Parent | on HN ]

Re:Things you can’t do in Rust (and what to do instead) by hu3 on Saturday May 15, 2021 @02:08PM (#27167488)

Yes but where is Lisp market share? It's mostly an academic language these days.

If anything Lisp current adoption proves that aiming to tackle both ends of the spectrum in a single language might not be a good idea.

[ Parent | on HN ]

Re:Things you can’t do in Rust (and what to do instead) by ta_ca on Saturday May 15, 2021 @02:44PM (#27167799)

do adoption or market share matter in this context? if you can have best of the both worlds why would you want to deal with an another language?

[ Parent | on HN ]

Re:Things you can’t do in Rust (and what to do instead) by astrange on Saturday May 15, 2021 @10:32PM (#27170737)

There are downsides to using the most powerful option at all times.

https://en.wikipedia.org/wiki/Rule_of_least_power

Also, Lisp is the most powerful at constructing programs but that means it's the least powerful in the field of making sure your program actually does what you wanted it to - that's what types, borrow checking, proof assistants and so on are for.

(Some people think Lisp is declarative because it's homoiconic but that's not true - you can't find out what a Lisp macro does without executing it.)

[ Parent | on HN ]