Re:Java at 30: The Genius Behind the Code That Changed Tech
by MaxBarraclough on Saturday May 17, 2025 @04:41AM
(#44012944)
I'm not sure what you mean here, as far as I'm aware data safety isn't standard terminology.
Re:Java at 30: The Genius Behind the Code That Changed Tech
by lazide on Saturday May 17, 2025 @07:56AM
(#44013655)
I think they’re using it in the context of what you’ll get without some degree of locking, which is data corruption and/or other issues.
It’s not that you need locking to use threads. You need locking to stop threads from ruining any shared resource/data they are both trying to touch at the same time.
You can use platform threads, user-space threads, language-provided "green" threads, goroutines, continuations or whatever you wish for concurrency management, but that's almost orthogonal to data safety.