Discover and read the best of Twitter Threads about #Androidev
Most recents (1)
This weeks @androidweekly included a post by @VasiliyZukanov that unfortunately perpetuates a myth in programming; it's ok to use threads.
Before I explain why this is myth that we need to kill, you should read the post: techyourchance.com/concurrency-frβ¦
#Androidev #Development
1/x
Before I explain why this is myth that we need to kill, you should read the post: techyourchance.com/concurrency-frβ¦
#Androidev #Development
1/x
There are a number of problems with the solution in this post, but I'm just going to focus on one; using low-level concurrency APIs (i.e., java.lang.Thread).
With very few exceptions (we'll get to those), this is always a bad thing.
2/x
With very few exceptions (we'll get to those), this is always a bad thing.
2/x
One simple argument against the use of using threads directly (regardless of language, platform or OS) is that we don't do it for other things.
You're not implementing your own HTTP client, UI framework, or database engine. So why would it be right for concurrency?
3/x
You're not implementing your own HTTP client, UI framework, or database engine. So why would it be right for concurrency?
3/x
