• 1 Post
  • 121 Comments
Joined 2 years ago
cake
Cake day: July 3rd, 2023

help-circle






    • it’s free
    • runs on a wider range of hardware
    • is more customizable
    • can run much windows software with wine or proton
    • has a large ecosystem of native software
      • much of it free and open source

    The advantage of Mac is it’s more widely used and thus more widely supported (for things that are supported at all). You can just buy an apple computer from a trusted source and it’ll work. Linux doesn’t quite have that yet. If more people move to Linux , you’ll find better drivers and stuff.








  • jjjalljs@ttrpg.networktoScience Memes@mander.xyzI dunno
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    12 days ago

    I like and respect teachers, but I’m a software developer and I’m telling you that adding extra parenthesis often adds clarity and makes the whole process smoother. You exist in a whole other context that has norms and assumptions that do not apply to what I’m talking about.

    You being technically correct is irrelevant.



  • jjjalljs@ttrpg.networktoScience Memes@mander.xyzI dunno
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    12 days ago

    That’s because it’s already clear as is, as per the rules of Maths.

    More people evaluate 2+3x4 incorrectly than 2+(3x4). So, no, your answer does not hold up to my observed reality. You can throw as many “well technically” and “well actually” as you want, but that’s not going to fix the bug or make a pr.


  • I’ve seen some garbage slide through code reviews. Most people don’t do them well.

    I’m doing contract work at a big multinational company, and I saw a syntax error slide through code review the other day. Just, like, too many parenthesis, the function literally wouldn’t work. (No, they don’t have automated unit tests or CI/CD. Yes, that’s insane. No, I don’t have any power to fix that, but I am trying anyway). It’s not hard to imagine something more subtle like a memory leak getting through.

    In my experience, people don’t want to say “I think this is all a bad idea” if you have a large code review. A couple years ago, a guy went off and wrote a whole DSL for a task. Technically, it’s pretty impressive. It was, however, in my opinion, wholly unnecessary for the task at hand. I objected to this and suggested we stick with the serviceable, supported, and interoperable approach we had. The team decided to just move forward with his solution, because he’d spent time on it and it was ready to go. So I can definitely see a bunch of people not wanting to make waves and just signing off on something big.