5 ms·

Why isn't it enabled by default?

by maxloh 3y ago

vesinisa 3y ago
There's probably a very good reason for it. I would definitely advice anyone against enabling "Developer options" on your phone without having a good understanding what those options do. They are hidden and hard to access for a reason.
- j1elo 3y ago
  Sadly they contain some options which ought to be part of the normal system settings, but they aren't. Such as animation speed. I hate _so much_ all the wobblyness of the GUI! Everything bouncing, sliding, and hovering around. Thankfully one can enable Developer options and set all that stuff to 0x, which effectively disables everything and now the system becomes crisp and instant, as it should be. Another essential setting for saving much precious battery, is to not have the cellular data active at all times even when WiFi is active. If I come home and enable wifi, I do not want the cellular data to stay active too in the background. It's much better waiting the couple seconds it might take to switch networks, in exchange for some extra juice.
  - tuukkah 3y ago
    Also, configure "Smallest width" to a high dp value to fit more content on the screen.
    - j1elo 3y ago
      For sure! that one is a very good candidate for basic option to tune on any phone. I always up it a bit to gain more screen estate.
helloooooooo 3y ago
Because it keeps catching poorly written code that hasn’t yet been fixed.
- benibela 3y ago
  Or clever code that should not be fixed I just added my own tagging to my pointers. I have 48-bit pointers and 16-bit of tagging data. I replaced all my struct { word type; char* data }; with something like (type << 48) | data. This saves a memory allocation and pointer indirection. It is much faster
muricula 3y ago
There is almost certainly a performance and battery life hit. Each pointer dereference will trigger a lookup in the MTE tag table, and a comparison between the pointer's tag and the table's tag. So you have a decently sized chunk of RAM set aside for the tag table, more memory bandwidth used up by table lookups, and the cost of the actual tag checks.

Why isn't it enabled by default?

by maxloh 3y ago

Why isn't it enabled by default?

There's probably a very good reason for it. I would definitely advice anyone against enabling "Developer options" on your phone without having a good understanding what those options do. They are hidden and hard to access for a reason.

j1elo 3y ago
Sadly they contain some options which ought to be part of the normal system settings, but they aren't. Such as animation speed. I hate _so much_ all the wobblyness of the GUI! Everything bouncing, sliding, and hovering around. Thankfully one can enable Developer options and set all that stuff to 0x, which effectively disables everything and now the system becomes crisp and instant, as it should be. Another essential setting for saving much precious battery, is to not have the cellular data active at all times even when WiFi is active. If I come home and enable wifi, I do not want the cellular data to stay active too in the background. It's much better waiting the couple seconds it might take to switch networks, in exchange for some extra juice.
- tuukkah 3y ago
  Also, configure "Smallest width" to a high dp value to fit more content on the screen.
  - j1elo 3y ago
    For sure! that one is a very good candidate for basic option to tune on any phone. I always up it a bit to gain more screen estate.

helloooooooo 3y ago

Because it keeps catching poorly written code that hasn’t yet been fixed.

benibela 3y ago
Or clever code that should not be fixed I just added my own tagging to my pointers. I have 48-bit pointers and 16-bit of tagging data. I replaced all my struct { word type; char* data }; with something like (type << 48) | data. This saves a memory allocation and pointer indirection. It is much faster

muricula 3y ago

There is almost certainly a performance and battery life hit. Each pointer dereference will trigger a lookup in the MTE tag table, and a comparison between the pointer's tag and the table's tag. So you have a decently sized chunk of RAM set aside for the tag table, more memory bandwidth used up by table lookups, and the cost of the actual tag checks.