‹ BackHN Continuity

Thread

Book review: Is parallel programming hard, and, if so, what can you do about it?

149 points · 66 comments · ahelwer

  1. bob1029 · · focus · HN ↗
    We should make developers prove they can use one core responsibility before we hand them 64.

    Much like we get pilots comfortable in single engine aircraft before we have them fly around in 747s and AC130s.

    1. trylist · · focus · HN ↗
      They're fundamentally different skills in my view. It's helicoptors vs fixed wing, rather than single engine vs multi engine
      1. bob1029 · · focus · HN ↗
        Rotary vs fixed wing is more like GPU vs CPU programming. Within each you still need to understand the capabilities of the machine before you can go wide effectively.
    2. pjc50 · · focus · HN ↗
      Many of the pieces of software which people claim are miserably slow are using one core irresponsibly. Usually because they're operating in a "only one thread can touch the UI" environment and that thread keeps blocking on everything.
      1. [deleted] · · focus · HN ↗

        [deleted]

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.