This proposal aims to as the name implies bring more structure to concurrent programming. This will be done by treating related tasks that are running in different threads as a single unit. Thus making it easier for us to manage the state, and also keep an eye on what’s happening.
Note: we won’t be diving into the synchronized keyword, or the Lock interfaces which offer additional capabilities compared to synchronized. But they’re certainly also worth looking into, but which flavour of lock fits best depends on your thread safety & performance requirements.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programming@programming.dev
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person’s post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
Follow the programming.dev instance rules
Keep content related to programming in some way
If you’re posting long videos try to add in some form of tldr for those who don’t want to watch videos
Or use ZIO. https://zio.dev
People be always trying to invent Erlang.