Alonely0
@theangriestbird @FragmentedChicken IMO it's great that they're settling for a unique brand look that's actually practical. Pixel's camera bump not only makes them usable on flat surfaces, but allows you to clamp-mount camera lenses on the bump itself. Personally, I really like the look & feel of my 6a.
@HidingCat @shaked_coffee @gelberhut @Humanius an 8th gen i7 is still a beast, even if most laptop ones only have 4 cores.
@blindsight @Apeeksiht my 6a's battery life w/ GrapheneOS is great. Not the best, but lasts a day of moderate use just fine. Days of heavy use I'll have to charge it in the late afternoon, and days of light use it's almost like I haven't unplugged it.
@gvasco @IdleSheep recently it's even slightly buggy too, but it's still orders of magnitude lower than stock.
@worfamerryman @FragmentedChicken android is less memory efficient, because Java in lots of scenarios basically allocates the double of the memory that it needs for performance reasons. However, android with 6 or 8 GB is fine for 99% of users. 24 GB is nuts, and it's probably just for gaming.
@skullgiver @LaughingFox It's not programmer laziness at all, RAM modules' size has to be of a power of 2 on most platforms because of various assumptions the CPU makes in memory alignment and memory bulk reads for performance reasons. Processors don't interact directly with the flash dies, so it's fine for them to be of the size they feel like provided the controller knows what it's doing.
@zikk_transport2 @Kyoyeou the cloud is someone else's computer, and I'd rather have my data on mine. I can understand why a normal user, who can barely manage their own computer, would want someone else to do it for them. But I am perfectly capable of doing my own backups and self-hosting random crap.
@ExLisper @aluminium Android and iOS have been intercalating featureful and polishing updates with each other for a while now.
@cheery_coffee @Klystron You have the option to also export to raw, so that you'll have the full sensor data, without lossy compression, processing or AI.
@soulsource @anlumo dude your whole code is UB. A reference
&
means that the data behind it never changes while any reference exists, allowing multiple pointers to point at it at the same time (aliasing); whereas a mutable reference&mut
means that the data behind may only be read or written by that pointer, i.e. multiple pointers (aliasing) can't exist. The compiler uses this to optimize code and remove stuff that you promise never happens. Always use miri, and go read the nomicon.