• 0 Posts
  • 148 Comments
Joined 11 months ago
cake
Cake day: December 24th, 2023

help-circle




  • You know what I figured out as a man? Just listen to the other party in this order of increasing priority: body language, facial expression, their words. MAIN THING TO AVOID: Never assume they are/will be comfortable with you. Never assume consent with body language or facial expression. If they want to be romantically involved THEY will approach you.

    Before I was married my mind was on alert talking women in order not to come off as creepy. This was with women whom I had purely platonic relationships like my coworkers or college mates. I am aware the effect men have with their staring. To this day when I am walking on the street I make sure to not walk behind women. If I can i overtake them. If not I just change directions even if my destination is straight ahead. Treating the nonfamily women in my life like I would treat men should be the right thing to do… but its not easy with the reputation that men have among women.

    So my point effectively is just don’t be creepy and pushy. Just be polite and reciprocate interest. Otherwise just treat them like your sister or guy friend.












  • I am quite cheeky for saying this but:

    How is it leaky if the default paradigm of any sequential program is the expectation that it will block? If i write blocking socket code I know my thread is blocked until read() returns.

    If i am writing async socket code I know to wait for poll or whatever it is that is the correct way to wait nowadays. My design would reflect that. The blocking is just moved to another thread effectively and this abstraction is packaged as a Future.

    Asynchronous code does not require the rest of your code to be asynchronous. I can’t say the same for blocking code.

    Well this is just stating a tautology isn’t it?

    Edit:

    It would be a Hurculean effort, and I don’t think it’s a sustainable approach. If you’re writing a higher level library, it would be a lot to ask to check if your dependency’s dependency’s dependency maybe reads from a socket.

    I guess I understand what’s the argument here.

    The author wants a safeguard against libraries that are blocking with compiler checks. I agree it is a nice thing to have. But they could have mentioned that without saying “blocking code is leaky abstraction”.