• 1 Post
  • 29 Comments
Joined 1 year ago
cake
Cake day: June 27th, 2023

help-circle



  • Getting anti-cheat that technically already works enabled on Linux has been a lot of work and Epic still won’t enable it. Piracy protection systems will also be an issue. Most EA games inspect your CPU to see if they like it on startup (I think this is using vmprotect and some non-OS x86 calls but don’t quote me on that). These kinds on anti virtualization checks are really common (not just in games ProctorU and lock down browser do them too). I don’t think valve running an open virtualization layer will be well received by companies and they will probably ban it from running games. MMOs (due to botting) and anything with anticheat will look particularly askance at this. I also suspect Valve won’t want to try hiding the VM signatures as it borders on violating DMCA.

    Newer games will probably get ported if a large part of the market buys into ARM. Unity stuff might get re-released as it is .net if the publishers can be bothered. Minecraft java edition will also always love you (the launcher might not though).


  • The main advantage of ARM right now is that there are low power cores available. The actual instruction set is unrelated to this advantage. If Intel or AMD put more serious effort into power efficiency most of the advantages go out the window.

    As for instruction set changes impacting what software you can run I think that is still a big issue. Yes porting to ARM is straitforward in more modern programming environments but most software actively developed at the moment has a lot of old cruft that won’t easily port if the engineers can even be convinced to touch it. Most businesses are dependent on old software not all of which is still maintained. Most gamers are even more tied to old software that is not going to get ported and often has annoying anti-virtualization checks (see games breaking on systems with enabled intel e-cores).

    I am not sure how large the modern non gaming personal pc market is (tablets, phones, works computers, and chromebooks probably took a chunk out of it) but that could be in play.












  • #2 is also the most insideous to update. Add another indented line to one of the conditions and the cotrol flow completely breaks while visually appearing fine.

    C and a number of other languages have annoying pair of parallel syntax systems that makes it easy for people to read code one way and computers to compile it another. People read the indentation and newlines while compilers count braces and semicolons. #2 gets rid of the braces and makes control flow driven by semicolons making human visual inspection more likely to fail