3 ms·
Though I'm sure you will, I would say give it some more time. My start with go was just like yours, but it quickly started to "click", and more robust patterns
by ominous_prime 14y ago
Though I'm sure you will, I would say give it some more time.
My start with go was just like yours, but it quickly started to "click", and more robust patterns began emerging more naturally for me. I don't think I can verbalize yet what has made the difference for me, but it may something like "structure your code around channels" vs "use channels to synchronize your code".
- jerf 14y agoYes, I'm not done. I am mostly just a bit disappointed that it still remains relatively easy to get into trouble with concurrency. It takes much more work to get in trouble with those other environments. It is a positive that it does scream bloody murder, rather than silently corrupting things or the other ancient failures of shared-state threading.
- siganakis 14y ago+1 for this! When I first started with golang I too was flailing around with deadlocks, but once you have spent a bit of time with it, it becomes obvious when you have messed up. I think that this is more of a lack of familiarity with the language rather than an intrinsic problem with golang.