this post was submitted on 13 Jun 2023
10 points (91.7% liked)

Programming

3347 readers
4 users here now

All things programming and coding related. Subcommunity of Technology.


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] rath 11 points 1 year ago (2 children)

It's hard if you have unprotected, shared mutable state. If you use a language that uses immutable data structures (Haskell, Clojure, Erlang) it's easy! If you use a language that won't let you share mutable data without the required protection (Rust) it's also easy! Everything else and you can be sure that even if it looks like it works, it most likely doesn't.

[โ€“] Syreniac 4 points 1 year ago

Even if you work in permissive langauges like Java, if you start from the position of "this code will need to be thread safe", its still not hard to do. The problem I've seen with more permsissive languages is that external libraries have bad systems built in and even if the code you write is threadsafe the external library csn introduce all sorts of weirdness.

For example in Java, the SimpleDateFormat class which is a fairly standard way of parsing/outputting dates and is the go to example in all number of tutorials is not inherently threadsafe (and that's part of the JDK!). Someone can write sensible stateless code and get tripped up by this.

load more comments (1 replies)