UI Thread Blocking
The cluster focuses on the single-threaded nature of UI rendering across platforms like web, mobile, and desktop apps, and the critical need to avoid blocking the main UI thread with heavy computations or I/O to maintain responsiveness using techniques like multi-threading or async operations.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Performance of UI is mostly single threaded
Usually because the said developers are too dumb and do everything on the UI thread.
It's common for all client apps to not block the main thread be it iOS, Android or Web
This only works if the UI library has good performance. During years this was a big issue in Java, and why it really needed multi-threading.
Sharing the UI thread with logic is something to be mitigated when building UIs, it's not a feature.
"don't block the ui thread" is a pretty classic aphorism in any language.
If you're actually doing busy logic then it'll block the UI thread, but you have to work pretty hard to do that, and IO won't block the UI thread
Could you please expand on what you mean by the 'ui not being blocked'.What behaviour do you expect the app to have and why?
No, not normally. It's fairly rare, and when it does crop up, it is typically handled with pre-baked solutions that are used to spawn a worker thread/process for the purposes of off-loading work from the main UI thread, with minimal communication with the main UI thread via posted messages.
It’s slowness reminds me of blocking on UI threads.