4 ms·
> Writing real multithreaded code without a GIL is hard. I'm starting to think this is going to be a major dividing line in developer skill going forward -- th
by hamburglar 6y ago
> Writing real multithreaded code without a GIL is hard.
I'm starting to think this is going to be a major dividing line in developer skill going forward -- those who can write threadsafe code and those who can't. There's an awful lot of Java, C# and Golang out there and if a programmer can't reliably think through thread safety issues (which is not that difficult in simple cases), they aren't capable in that realm.
One of the most frustrating things about my brief excursion into the land of Ruby was that the community was full of modules written by people who had no reason whatsoever to think about thread safety because they were programming for Rails, not Ruby in general.
- valand 6y ago> those who can write threadsafe code and those who can't This, abstracted, those who can write distributed software and those who can't yet. Dealing with shared resources is similar to dealing with shared memory if you zoom out a bit. We need more people to move from the latter group to the former, for reasons. The more people aware of distributed software and its challenges, the better.
- jashmatthews 6y agoThis sounds very gatekeepy. The JVM and Golang have additional aides for writing thread-safe code because writing multi-threaded code is fucking hard. People at the top of our field working on browsers or VMs regularly fuck up the simple stuff. If it was easy we wouldn't have Erlang or Rust.
- hamburglar 6y agoI'm very gatekeepy about only wanting competent developers working on my code.