

hmm It’s a bit of a hassle right now…



hmm It’s a bit of a hassle right now…



In theory, moving over to 16KB has quite a few benefits. Each page table maps 4x the memory, resulting in fewer memory accesses and better cache coverage, improving performance and power efficiency. There are trade-offs, however.
Internal memory fragmentation is slightly worse, resulting in some additional RAM being wasted when apps request small amounts of memory. Android itself has been page size agnostic since Android 15, but that doesn’t mean older applications are. Many older “native code” applications (such as those written in C or using the Android NDK) were built with 4KB pages in mind and need to be rebuilt with 16KB alignment (which remains 4KB-compatible as well). Google expects that most apps built with Kotlin are already compatible, but this is still a potentially significant developer burden. It presents a particular problem for apps that are no longer maintained or use libraries that have not yet been updated.


off by one error


I hate making out wearing glasses. That said, it is a porn category 🤷♂️


laying them off might save their lives, they should find another job


at least 2 breeding heifers


There’s no reason to believe it’s mostly unsafe. And even if that’s the case, changing from unsafe rust to safe is less of a leap than cpp to rust.


no shit, pick any post that mentions AI here and see who are the first ones to comment every single time.
If you don’t want a “cycle of negativity”, maybe let’s not throw rocks at anything for just bringing up the topic?
how’s acknowledging this herd behavior contributing to it. Some of us are also tired of reading the same crap in the comments.


It’s not a why not response. I’m asking back why do you think it wouldn’t be worth it even as a literal translation from C++, because in my view, that would be a first step towards a proper Rust port, and it still brings benefits to the table.


I’d give her a pass for being 15


Why it wouldn’t be? Surely not having idiomatic rust doesn’t eliminate other benefits of switching to the language, like better tooling, memory safety, and perhaps more people willing to contribute. Over time the codebase can be improved but the main goal in the transition seems to not break existing functionality, which they seem to have accomplished for LibJS.


out of context?
Please coordinate with us before starting any porting work so nobody wastes their time on something we can’t merge.
If you look at the code, you’ll notice it has a strong “translated from C++” vibe. That’s because it is translated from C++. The top priority for this first pass is compatibility with our C++ pipeline. The Rust code intentionally mimics things like the C++ register allocation patterns so that the two compilers produce identical bytecode.
that seems reasonable to me


yeah, this part of the community is as insufferable as the overly enthusiastic vibe coders


they do, especially the billionaire ones


idk what to tell you, because I just tried it and it works


ah, this puts it together and it’s exactly what I was looking for, thanks


ah yes, I stopped watching the guy because of that and the clickbait, but he does make some interesting content sometimes.


so you haven’t tried it recently
words? Where we’re going to we don’t need words
imagine government regulating what kinds of feelings are allowed in mind ads
we’re screwed