• 0 Posts
  • 17 Comments
Joined 1 year ago
cake
Cake day: July 27th, 2023

help-circle
  • That’s not what is surprising.

    Gaming under emulation is not exactly easy stuff even under optimal conditions, when your drivers and userland are not experimental/hacks and you are running on the same architecture - try doing AAA gaming on Linux using a windows VM and you will see.

    Setting aside gaming for a moment, cross-architectural emulation is stupidly slow because it cannot use any hardware features, it’s all software work on the cpu. Do you have a Linux machine? Try downloading a Firefox binary for another architecture (aarch64 for example) and run it, try watching a youtube video, if you haven’t died of old age in the meantime. Now Apple has this rosetta magic thing to emulate x86, but it was never meant to run (and it was never used before) on bare metal Linux.

    Now what happens here is that there is a vm that runs a vm of a different architecture (arm 64k vs arm 4k) that runs another vm of different architecture (x86), and somehow you can game on it with competitive performance. All of it with a dnf install.

    Simply put, this is unheard of.






  • That was exactly my point. Blocking instances because “that way my content can’t be seen there” doesn’t make sense, because it’s trivial to bypass it. Yes, even a screenshot will do the job if nothing else, so why talk about protocols in the first place?

    Somebody (maybe you maybe not, can’t check while replying) said that blocking instances was useful so that “my content doesn’t get seen / shared / pushed / etc to people and instances I don’t want”. That doesn’t make sense because of the line above. If you need clarification on who are those people and what are those instances ask them, not me.

    I hope I’m somehow conveying my message. If there is a subtlety in the subject that I didn’t catch feel free to help me understand.