This is incorrect. The inclusion of if isn't a matter of legacy, it's because if is a low level primitive that can be used to build higher level abstractions. That is why Lisp has if; the thesis of Lisp is to expose a small set of primitives, allowing developers to leverage those primitives to build the language they need. While I agree that many developers reach for if when a higher level of abstraction would be more appropriate, there should be no golden rule to "never use if". Sometimes a lower level of abstraction is what is appropriate for a task.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is incorrect. The inclusion of
if
isn't a matter of legacy, it's becauseif
is a low level primitive that can be used to build higher level abstractions. That is why Lisp hasif
; the thesis of Lisp is to expose a small set of primitives, allowing developers to leverage those primitives to build the language they need. While I agree that many developers reach forif
when a higher level of abstraction would be more appropriate, there should be no golden rule to "never useif
". Sometimes a lower level of abstraction is what is appropriate for a task.