Did you actually read my comment? It’s actually impressive to get those takeaways from that…

Anyway, if you want to twist my comments into something that makes yourself pointlessly mad I can’t stop you. Your definition of an android game seems to be Google Play malware, so I don’t think you’ll ever get what you want.

When I’ll get games comparable to like FFX or Shadow of the Colossus (the first two that come to mind) I’ll finally be satisfied with android gaming.

Again, indie games exist and can easily be run on most phones through Winlator/GameNative. The Nintendo switch is basically an 8 year old midrange phone processor and that still got games, plenty of steam titles will run fine on even a low/midrange android phone.

Until then all the p2w shit and other crap, or even 5yo PC games at low graphic settings on flagship phones, won’t cut it.

So you want games comparable to what came out in 2001 and 2005, but a 5 year old AAA is too old for you? What???

Luckily my current phone will probably be my last android device too.

If you’re saying this because you’re switching to iPhone, I wouldn’t get my hopes up on the situation improving. It’s equally as bad on iOS. If you’re saying that because you’re getting a Linux phone or a non-smartphone, fair enough but those don’t have any games, let alone emulated ones.

Also, emulating is very cool, however what’s the last AAA PC game you played in your phone?

Excuse me for sending an incredibly clickbaited YouTube video, I don’t play AAA’s since honestly IMO they’re not as good as indies anyway. However, according to this cyberpunk runs (albeit I’m guessing that’s on low) on newer phones: https://youtu.be/ACPXNADIjKw

I’m sure other AAAs from even just a few years ago could run fine. The only problem is that most android phones don’t have enough storage for AAAs anyway. A “native” android release wouldn’t change that.

Also wine is not an emulator, as its name clearly states, it makes things run natively so we should more generally talk about “PC gaming” there.

If you still want to make a distinction between games born for Windows and games born for Linux, then yes, those are not “Linux gaming”.

So is the line you’re drawing the emulation layer needed between ARM and x86? Or is it the difference between emulation and translation?

If this exact same fex+proton software was run on a snapdragon laptop under Ubuntu is that really that different? Do you count apps running under Java bytecode as emulation? Because that’s a vast majority of android apps. The distinction between translation, native gaming, and emulation is ultimately kind of meaningless if you get a good experience out of it.

Android is technically Linux under the hood, so it can (and has) been making use of the improvements to Linux gaming.

If by “android gaming” you mean you want to see a world where games are published to the play store in addition to Steam and consoles, you should probably give up on that. The play store is too ridden with actual malware to make that a reality. Even if games got released there, people would complain that they aren’t free because all of their other phone games are. If you want to play games on your phone with a Bluetooth controller and get a decent experience, it’s already here.

Honestly if I can play all of the new indie games on my phone I don’t really care whether or not they’re “android games.”

By your logic the steam deck doesn’t have any games since most of them rely on proton to work.

There are android apps combining fex/box64 with proton in order to run full Windows games now. Android may actually be a semi-viable gaming platform in the near future.

GameNative is one that works as a full steam client but there are a few others that give you more control like Winlator (both on GitHub)

You can actually play games pretty decently on them, especially indies like hollow knight and Celeste.

VR is a niche market with fundamental accessibility flaws (motion sickness, spatial requirements, etc.). As for the controller, what discussion is needed? The steam deck already exists and from that it’s pretty easy to get a decent idea of what the controller will cost and feel like. It’ll probably end up being a solid controller for people that want it, but uncomfortable for people with smaller hands.

That isn’t to say that the steam frame/controller won’t impressive pieces of technology, but should be pretty easy to see why discussions would mostly be around the steam machine and specifically its pricing. Its success (or failure) will likely be what carries the reputation of both the steam frame and the steam controller alongside it.

If you want to be technical about it, you pretty much just described any modern video game console. The OS is the only thing actually differentiating modern consoles from PCs (or tablets in Nintendo’s case).

Really begs the question of what language even means

Then it really is authentic Boston Pizza!

(No seriously I found maybe 3 good pizza places while I lived in Boston and I’m pretty sure 2 of them technically weren’t even in Boston. The pizza there is mid at best)

It’s worth noting that support for pixel 10s is currently in alpha and incredibly buggy

Is raccoon still being developed? The last commit that isn’t a dependency bump was 3 months ago and the last release was 8 months ago. I’m still using it for now because I like the UI but I feel like a lot of the formatting is kind of jank

I think the problem is that roads not designed for bikes in Europe are also old enough to have not been originally designed for cars, so things usually end up working out to some degree.

In the US (especially for infrastructure built from scratch in the 1900s onward, i.e. most of the US except for some parts of the east coast) most roads and town layouts were designed specifically around cars and travelling at car speeds, and are explicitly hostile to anyone who isn’t travelling in the biggest truck you’ve ever seen in your life. Blame oil/motor companies for bribing politicians throughout the 1900s (and honestly still today)

The company says it is now developing an “advanced flow that allows experienced users to accept the risks of installing software that isn’t verified.” This installation flow will include safeguards to protect people who are being coerced into installing a dangerous app, or tricked by a scammer, along with “clear warnings to ensure users fully understand the risks involved.”

Seems like there will also just be a toggle somewhere (probably developer settings) that lets someone install from any source

Isn’t the content blocked because imgur refused to implement ID-based age verification so as a result they just blocked users in the UK? Or am I missing something else here

Or source code at this point, AOSP is still missing the 16 QPR1 release that came out for pixels at the beginning of September

Release QPR1 source code first though it’s been 2 months 😭

(Or at the same time, that would be good too)

I think a lot of the confusion comes from the ambiguity of the phrase “memory leak.” Rust is designed around preventing insecure memory access (accessing out of bounds for an array, use-after-free, etc.) and devs call that a memory leak. But another form of memory leak is just not freeing up memory when its no longer needed (e.g. continuously pushing a bunch of things to a global vector and never clearing it). That is more of a fundamental program design issue that rust can’t do anything about. (and really, neither could any turing complete language)

‘Use-after-free’ bugs are a specific type of memory access bug that Rust was designed around preventing. It literally refers to trying to access a block of memory after it has already been freed by the memory allocator. Unless you go out of your way to use the “unsafe” keyword in rust (which in most cases, you shouldn’t) then this type of bug is not possible.

Do you know what a use-after-free bug is? Rust was literally designed to make this type of memory bug impossible.