search

vinegarhq / sober

Runtime for Roblox on Linux
https://sober.vinegarhq.org/
172 stars 6 forks source link

Arm64 support #166

Open thenameisluk opened 3 weeks ago

thenameisluk commented 3 weeks ago

Before Creating the Enhancement Request

Is your feature request related to a problem?

yes, lack of accesibility on specyfic platform

Describe the Solution you'd Like

provide a build/support for arm64 linux

Describe Alternatives you've considered

there aren't really any, x86 emulator would be really slow can't find source code so can't really compile it myself

Additional context

lack of support for arm64 prevents ppl on

and other

from using this software. it likely shouldn't be that much work to compile it for arm64 it would be very appreciated if arm64 version was also provided just like with minecraft bedrock launcher

KonoKore commented 1 week ago
  1. install android on pi
  2. the scale of AsahiLinux is almost close to 0
  3. ARM ChromeBooks can already run ROBLOX

Plus the fact that dealing with another architecture, is a pain in the ass image

thenameisluk commented 1 week ago
  1. in that case project is pointless since everyone can just get waydroid, another solution on x86_64 just install windows :3 linux is 4% anyway
  2. doubt u can measure that, again linux has only 4%, your project users or close to none in that scale
  3. not really that simple, there are other arm64 laptops that run pure linux but ig these either aint big enough for you to care

if u really think it's not going to happen just close the issue, noone can force you to do anything don't think anything productive will come out of this being open anyway

KonoKore commented 1 week ago
  1. Sober runs the x86_64 Android version via a compatibility layer, with the way that Android is optimized, you get 2x the native performance than on windows, and before Vinegar was doomed to fail.
  2. At least 90% and over of Linux users are on x86_64 hardware, that puts the percentage of Asahi Linux users down to 0.5%, and again, dealing with another architecture is a hassle
  3. Again, same argument for number 2

As I am not a maintainer, you can close the issue yourself.