@alexcleac
slightly related:
https://github.com/ziman/idris-py/issues/2
null / nil / None was a mistake
@alexcleac "good and efficient" is pretty vague tbh, if the code doesn't produce the correct result, it doesn't matter how fast it is.
@grainloom Businesses often say that nice result today is better than great one tomorrow :D However I agree with you on this - small bug can cost a lot more to business that an hour of qualified professional work
@grainloom Hard to tell. Much of nowadays programmers became such because it is pretty to write the code nowadays. And thus is thanks to null/nil/undefined/None.
In fact, when you start writing some language that have a sane way to handle optionals (like #rust #scala #kotlin etc), it becomes harder to write good and efficient code, because it requires a bit more thinking from you. Code is safer, but you have to use your head. And mass doesn't want this, they just need to make another unicorn startup