3 ms·
>Concurrent programming is hard because "concurrent programming" usually means "concurrent programming with mutable states and imperative control constructs" p
by trhway 12y ago
>Concurrent programming is hard because "concurrent programming" usually means "concurrent programming with mutable states and imperative control constructs"
people have trouble even with database transactions - the simplest "imperative with mutable" concurrency model around. The simplicity comes in particular from well-defined hierarchy of objects and locking semantics upon them. No wonder that programs with concurrency, especially written in OOP languages where mutable state hidden, spread around in really disorganized way and de-facto inter-mixed with code, is just a mess. The article mentions Netbeans - yep, UI OOP models are among the messiest.