3 ms·
This was exactly my thoughts ... I'm still trying to figure out why they would use multi-threading though.
by biznickman 14y ago
This was exactly my thoughts ... I'm still trying to figure out why they would use multi-threading though.
- frankus 14y agoWha? The UI needs to keep processing events to remain responsive. If you have a long-running (relatively speaking, say 10 milliseconds) process like uncompressing an image, you don't want your UI to lag for that long. You could have the image decompressor look up every millisecond or so to see if there are any UI events to process, but that leads to the sort of spaghetti code that multithreading/multitasking was built to address.
- jonathannorris 14y agomulti-threading is a must for every iOS app. If you are building a fully single threaded iOS you are going to have a bad time.
- pdenya 14y agonot sure if you're an obj-c dev but for me the surprise was that it even needed to be mentioned since it's extremely easy and common place to do processing outside of the main thread in current apps.
- duaneb 14y agoBlocking the UI with requests is a UI no-no.