GURLSSS HATI2 LAGIH YAA HUWE GUE MASIH TAKUT SM WAWAN KURAWAN… hati2 kl mau upp di thread2 beginiii gurlss🫶🫰

Tbh, TL mulai jarang ada yg lewat thread2 bermanfaat gratis sekrg ya... Karena ada pergeseran perilaku user scr masif. Niche seolah udh gak lagi penting.

figured we'd be able to @ threads by name or at least project. coming soon, or am I just missing something? currently if I want thread1 in projectA to tell something to thread2 in projectB, I'm contextmenu-copying the session id of the thread2 and giving it to thread1. not ideal

#Thread2 Concerns over limited pain medication in rural areas were also raised. Stay tuned for more updates #HOSPAZ #MembershipCoordination2026 #CompassionInAction @PCAUganda @healthtimeszim @WHO @MCAZofficial @PGHZIM

#THREAD2 L’armée congolaise a réussi à reprendre la cité de #Minekenge, Kalingi et une partie de Kakenge. Ce dimanche, des combats intenses ont été signalés dans la région. La société civile de #Minembwe rapporte plusieurs dégâts du côté des civils et des maisons détruites.

belum bikin kak, takut juga aku soalnya belum jago, nanti aku bikin thread2 pemula aja ya tapi setau aku di @happenfed ada 💗☝🏻

gue terlalu malas buat mantengin thread2 yg isinya list scammers kayanya kalo gak dari kenalan2 gue skip deh terlalu trust issue wkwkw

Say we have two threads: "Thread1" & "Thread2". If Thread1 is executing in method 1, can Thread2 then execute in method 2?

Learnt this the hard way long back. synchronized locks the object instance to a thread. So Thread2 will remain in BLOCKED status even if it enters method2. Once Thread1 releases it, Thread2 will acquire the lock on the object, in this case, "this"

Both threads are trying to run on this which means simultaneous execution not possible, because thread1 locked entire this object so thread2 has to wait ubtil thread1 completes its execution and releases the lock.

Yes, they can. Synchronized in Java locks per object instance. If Thread1 holds method1 and method2 is synchronized separately, thread2 can run method2 unless the synchronization shares the same lock. The real complexity emerges when you realize synchronized methods all lock the same object instance (this). So if both are synchronized, thread2 must wait for thread1 to release the lock. Method boundaries don't create separate locks; the object does. Most teams discover this late: they add synchronized to everything for 'safety', then production performance craters under load because all threads serialize on one lock. The cascade effect is brutal, one lock contention point stops the entire application. The fix was atomic operations on primitives, separate ReentrantLock instances for different concerns, and understanding that 'synchronized' is a mutual exclusion strategy, not a universal safety device. Context matters.

No, not on the same object instance... Both methods are synchronizing on: synchronized(this) which means they use the same monitor lock. If Thread1 enters: method1() and acquires this lock, then Thread2 trying to execute: method2() on the same object will block until Thread1 releases the lock...

Pedoq dok post screenshot thread2 bodoh macam tu pon aku dah rasa semak

#Thread2 6-Previous marking is invisible to both evaluaors. 7-Suppose a student previously got 0.5/3 mark, this time no guarantee he will get full mark. 8-Marking is tight in fear(teacher) 9-Teachers can't see and evaluate as per students requirement. #CBSEReevaluation #CBSE #OSM

Disuruh kasih bukti malah mencla mencle lambenya yaudah lah ya mau digimanain juga 😄 Thread2 aku ya suka2 aku lah mau hapus gak mau lapor apa gak.