Learning Common Lisp to beat Java and Rust on a phone encoding problem

Re:Learning Common Lisp to beat Java and Rust on a phone enc... by SZJX on Saturday October 02, 2021 @05:24AM (#28727257)

> It's also dynamically typed which disqualifies it for large collaborative projects.

That’s a quite absolute statement. At least Erlang/Elixir users would tend to disagree. “Dynamically typed” can still represent a huge variety of approaches, and doesn’t have to always look like writing vanilla JavaScript for example.

[ Parent | on HN ]

Re:Learning Common Lisp to beat Java and Rust on a phone enc... by kubb on Saturday October 02, 2021 @06:09AM (#28727434)

I hear your argument as "there exist dynamically typed languages therefore the benefits of typing don't matter". To be positive I'll say that it's better than the pendulum argument.

I'm aware that there exist dynamically typed languages in which large projects are written, I'm saying that they would be better off with type safety.

[ Parent | on HN ]