3 ms·

John Carmack has a take on it; https://twitter.com/ID_AA_Carmack/status/1592560938208710659?s=20&t=okwnHrPxZ2yPWKyTED5K7w https://twitter.com/ID_AA_Carmack/sta

• nicoburns 4y ago
  I think I agree with Carmack on this. I'm hyper aware of case now, but this was probably the major cause of errors for me when learning (didn't help that tooling was less good then, so there were no linters pointing out my errors).
  • derbOac 4y ago
    I guess for me it's one of those things I got tripped up on initially but came to appreciate later. It taught me how to be more precise about characters and reasoning about them in code. There's also cases where case sensitivity should matter in naming in my experience, and it's not possible without it.
    • UxDnz0 4y ago
      Personally this preciseness is just a distraction, but it sounds like you have learned from the constraints and can now take the training wheels off again. Very curious about those cases, yet to find one myself that was not because of a bad design decision. Though I am also very big on the idea of `ambiguous grammar, rigorous implementation`, for natural language too. (Toki Pona is a somewhat extreme example but the contextual grammar, and holistic minimalism is fascinating) Not to make it longer than needs to be; But take the example code in this readme: https://github.com/guzba/mummy https://github.com/guzba/mummy Being able to quickly script this without thinking about cases or style on the first pass is a really lovely way of reducing friction imho.
    • arc776 4y ago
      > There's also cases where case sensitivity should matter in naming in my experience, and it's not possible without it. I'm really curious, do you have any examples? I can't think of any that wouldn't be better served by using the type system.