Core Data struggles with Swift concurrency

Core Data, designed before Swift's modern concurrency features, wasn't built to handle async/await natively, leading to awkward workarounds. Developers often find themselves juggling background contexts and perform blocks to manage concurrency, which increases complexity. Type safety also suffers, as Core Data relies heavily on string-based keys for attribute access, bypassing Swift's strong typing. This can lead to runtime errors that compile-time checks would normally catch, making debugging more difficult. The lack of expressive code stems from Core Data's verbose and often boilerplate-heavy syntax. Swift developers accustomed to concise and expressive code find Core Data's API clunky and less intuitive.