Comparing the Same Project in Rust, Haskell, C++, Python, Scala and OCaml

Re:Comparing the Same Project in Rust, Haskell, C++, Python,... by galaxyLogic on Saturday June 15, 2019 @10:51PM (#20193559)

That is a good point worth emphasizing.

It is well-known that teams cause overhead. Think of the Mythical Man-Moth.

But in the end the other teams had 3 people that were able to maintain and develop their project further, if needed. The single-person team had only one such person.

[ Parent | on HN ]

Re:Comparing the Same Project in Rust, Haskell, C++, Python,... by pm90 on Sunday June 16, 2019 @12:07AM (#20193787)

But the Python code was also smaller. Easier to learn and maintain.

[ Parent | on HN ]

Re:Comparing the Same Project in Rust, Haskell, C++, Python,... by blumomo on Sunday June 16, 2019 @02:58AM (#20194214)

"Smaller code" does not mean easier to understand. It just means less characters to read. Maybe those characters are heavily loaded with meaning, as in the case with meta programing. You might need twice as much time to _understand_ the Python Code vs. the Rust code. The Rust code might be easier to extend, etc. So this is all comes to trade-offs at the end. All this being said, I'm still a huge Python enthusiast.

[ Parent | on HN ]

Re:Comparing the Same Project in Rust, Haskell, C++, Python,... by gmueckl on Sunday June 16, 2019 @06:39AM (#20194860)

Smaller code may also mean more entangled and more rigid design. But that is hard to tell from just the line count.

[ Parent | on HN ]