Why Android has so many Bit flags instead of EnumSet?

Question

I am learning android. I never used Bit flags in my life. So I bit explored to understand better. And I came across this article.

http://eddmann.com/posts/using-bit-flags-and-enumsets-in-java/

As the author suggests EnumSet is way more helpful than bit flags. But still why android framework used lot of Bit flags instead of EnumSets. Is there any specific reason to chose this hard way?

https://stackoverflow.com/questions/32360537/when-is-it-good-to-use-enum-in-android#comment52594240_32360537 — CommonsWare, Feb 05 '17 at 19:14
It is hardly recommended to use enum, as this will take up your memory double than the static block. — Aman Shekhar, Feb 05 '17 at 19:21

score 1 · Accepted Answer · answered Feb 05 '17 at 19:18

Performance. I'm about to have CommonsWare downvote and disagree (we've argued about this on the site at least once before), but enums are strings. Bit fiddling is far more efficient. Constant string comparisons are inefficient In frequently run code like the framework, its best to avoid inefficiencies by design. Java just relly screwed up on enums by making them strings instead of integers.

Why Android has so many Bit flags instead of EnumSet?

1 Answers1