Iwasawa 🌟 (one hikari of too many)

(replying to Iwasawa 🌟 (one hikari of too many))

‪there is no destiny for these devices other than e-waste and it is fucking painful‬

1 replies →
1 replies

sweet little raquel

(replying to Iwasawa 🌟 (one hikari of too many))

@hikari is that not something that could be changed on the software side when they do decide to kill off 32 bit for good?

Iwasawa 🌟 (one hikari of too many)

(replying to sweet little raquel)

@fishtrauma unfortunately android phones essentially do not get os updates

Iwasawa 🌟 (one hikari of too many)

(replying to Iwasawa 🌟 (one hikari of too many))

‪the fact that 4GB is considered a small amount of memory is extremely jokerifying also. iPhones have delivered a premium 64-bit experience both with that much memory and with half that. Android is an absolutely wretchedly inefficient platform. skill issue skill issue skill iss—‬

1 replies →
1 replies

Mia ‘Meetings? I Abstain’ Luna Tearmoon

(replying to Iwasawa 🌟 (one hikari of too many))

@hikari tbh Windows NT 4 delivered a premium 32-bit experience with 64 MB RAM, with noticeably lower interface latency

I will never stop being weirded out by how much RAM modern apps need

Iwasawa 🌟 (one hikari of too many)

(replying to Iwasawa 🌟 (one hikari of too many))

‪the absolute worst thing, that pisses me off more than anything else, is that ofc making an Android phone that supports both 64-bit and 32-bit is an option when building the OS image, or even better, just 64-bit. but Google said they'd start mandating the opposite. i'm serious‬

Iwasawa 🌟 (one hikari of too many)

(replying to Iwasawa 🌟 (one hikari of too many))

‪obviously that mandate was not for phones with lots of RAM. they said they'd mandate only supporting 32-bit specifically on brand-new 64-bit low-memory phones. to reduce the number of configurations they had to worry about.‬

‪i do not know if they went ahead with it but SCREAMS

Iwasawa 🌟 (one hikari of too many)

(replying to Iwasawa 🌟 (one hikari of too many))

‪ARM GAVE YOU THE WORLD'S SMALLEST 64-BIT-CAPABLE CORE TWELVE YEARS AGO AND THIS IS WHAT YOU CHOOSE TO DO WITH IT? THIS????? DOES YOUR LUST FOR INFLICTED SUFFERING KNOW NO BOUNDS, GOOGLE? DO YOU NOT LOOK UPON YOUR CREATIONS AND WEEP FOR WHAT YOU HAVE DONE. WHY DO YOU CURSE US‬

1 replies →
1 replies

Saagar Jha

(replying to Iwasawa 🌟 (one hikari of too many))
@hikari ARM had 64-bit cores in 2012?

Iwasawa 🌟 (one hikari of too many)

(replying to Saagar Jha)

@saagar yes. in the ruins of our civilisation, they will know us by the Cortex-A53 chips

Saagar Jha

(replying to Iwasawa 🌟 (one hikari of too many))
@hikari Ah ok so this is the typical ARM-brain at work. Yes it was “available” in 2012 (in the form of IP of course) and then it took at least two years for anyone to actually ship it

Iwasawa 🌟 (one hikari of too many)

(replying to Saagar Jha)

@saagar sure, that's the typical lead time. anyway that means we've been making cortex-a53 phones for an entire decade now

Saagar Jha

(replying to Iwasawa 🌟 (one hikari of too many))
@hikari And we shall make them for a decade to come

Iwasawa 🌟 (one hikari of too many)

(replying to Saagar Jha)

@saagar at the end of the world, there will be famine, pestilence, and Cortex-A53

Iwasawa 🌟 (one hikari of too many)

(replying to Iwasawa 🌟 (one hikari of too many))

‪if this does blow up then please do not follow me for technology opinions. you'd be enabling my worst tendencies. i am here to post about kanbaru suruga from the monogatari series and also how pretty the sky is‬