• 0 Posts
  • 630 Comments
Joined 2 years ago
cake
Cake day: September 2nd, 2023

help-circle
  • No. The problem is that kids have nothing else to do. The only fun thing left is the phone.

    They can’t go alone and play out there, they may get hit by a car or their parents might get in trouble. They have to always be supervised by an adult, but there are almost no places with adults to watch for the kids, they have to bring their dedicated parent. And parents have to work way too many hours, they don’t have time to watch the kid play for all the time the kid needs to play.

    Furthermore, everything that is fun to kids is illegal. “No skating here”, “no playing with a ball here”. Where can kids play? They don’t have a car to go to a remote place where playing is allowed. They should have areas where they can play relatively close to home.

    And I say this as a European. In America all these problems are 10x worse, I can’t imagine what that would do to a kid. Maybe the suburbanites can play in their lawns. But the ones in cities are out of luck.


  • That’s not true at all.

    My gf has awful logical reasoning skills. Which leads to her being wrong on many small arguments that can easily be proved with simple logic.

    There is no amount of reasoning that will make her change her mind. So in the end, she is always right because there is no other option. That is incredibly frustrating and I end up being neither “right” nor happy.














  • I know this thread is old. But I disagree with you.

    I agree that depending on how you use a debugger, some race conditions might not happen.

    However, I don’t agree that debuggers are useless to fix race conditions.

    I have a great example that happened to me to prove my point:

    As I was using a debugger to fix a normal bug, another quite strange unknown bug happened. That other bug was indeed a race condition. I just never encountered it.

    The issue was basically:

    1. A request to initiate a session arrives
    2. That request takes so long that the endpoint decides to shut down the session
    3. A request to end the session arrives

    And so handling the session start and session end at the same time resulted in a bug. It was more complicated than this (we do use mutexes) but it was along those lines.

    We develop in a lab-like condition with fast networking and computers, so this issue cannot happen on its own. But due to the breakpoint I put in the session initiation function, I was able to observe it. But in a real world scenario it is something that may happen.

    Not only that, I could reproduce the “incredibly rare” race condition 100% of the time. I just needed to place a breakpoint in the correct place and wait for some amount of time.

    Could this be done without a debugger? Most of the time yes, just put a sleep call in there. Would I have found this issue without a debugger? Not at all.

    An even better example:

    Deadlocks.

    How do you fix a deadlock? You run the program under a debugger and make the deadlock happen. You then look at which threads are waiting at a lock call and there’s your answer. It’s as simple as that.

    How do you print-debug a deadlock? Put a log before and after each lock in the program and look at unpaired logs? Sounds like a terrible experience. Some programs have thousands of lock calls. And some do them at tens of times per second. Additionally, the time needed to print those logs changes the behaviour of the program itself and may make the deadlock harder to reproduce.