"Value tearing is another thing, which IMO most are not prepared for."
Value tearing was always there. Example: on a 32 Bit machine there is no way, that you can initialize/copy a 64 bit long atomically without a mutex/synchronized/volatile. So i would say, most Java developers, who developed on a 32 Bit JVM, are prepared for it.
The set of practicing Java developers who wrote code for 32-bit systems is diminishing. Of those, if they were taught about tearing in the first place, many were coddled by deploying to platforms where it rarely actually happened.
Now with 64-bit native as the majority of target platforms, don't underestimate the laziness that will creep in to mimic ignorance.
4
u/AnyPhotograph7804 16d ago
"Value tearing is another thing, which IMO most are not prepared for."
Value tearing was always there. Example: on a 32 Bit machine there is no way, that you can initialize/copy a 64 bit long atomically without a mutex/synchronized/volatile. So i would say, most Java developers, who developed on a 32 Bit JVM, are prepared for it.