3 ms·
The answer as a whole is serious, I said as much, read again. A singled out this one point, because it is not. It is akin to any other knee-jerk dismissive att
by pseudony 2y ago
The answer as a whole is serious, I said as much, read again.
A singled out this one point, because it is not.
It is akin to any other knee-jerk dismissive attitude to anything different.
Casting away a far more proven language, used for over a decade in thousands of serious, commercial projects with wide editor (and LSP) support etc over indexing conventions, is not serious.
Lua is my first 1-indexed language, i have yet to have a single bug over this. It's a irrational fear.
- IshKebab 2y ago> A singled out this one point, because it is not. It absolutely is. I gave you concrete reasons. (Edit: actually in a sibling comment) > i have yet to have a single bug over this. I never said anything about bugs.
- TylerE 2y agoNitpick: you haven’t found any bugs. That doesn’t mean they don’t exist.
- pseudony 2y agoYes. So there may be a price to pay, one day. But a vague, unsubstantiated feeling that one day, you might introduce a one-off indexing bug should not justify discarding Lua, and all its substantial benefits over project. Arguing the pro's of Rust data-structure interop in case of a Rust project - that makes sense. This, this is basically nonsense.
- IshKebab 2y ago> But a vague, unsubstantiated feeling that one day, you might introduce a one-off indexing bug should not justify discarding Lua, and all its substantial benefits over project. Nobody said anything like that. There's no vague feeling of indexing bugs; there's a concrete degradation of code quality. And yes it's only one factor, not a deal-breaker. Nobody here said it was.