Yeah I agree, but it’s nothing to show offI just spent 2 hours yesterday after work playing some Dungeon Keeper - 1997. Before I played StartCarft 2 - 2010, and WoW - 2005. Those old games are more fun than most new games.
Yeah I agree, but it’s nothing to show offI just spent 2 hours yesterday after work playing some Dungeon Keeper - 1997. Before I played StartCarft 2 - 2010, and WoW - 2005. Those old games are more fun than most new games.
It's exactly just the binary. That's one of the things which differenciates x64 and Arm: the format of the executable binary.You can’t run an app compiled for x64 on ARM. So it’s not just binary.
iOS doesn't run x64.Coincidentally, Windows, macOS, Android, ChromeOS, and iOS all run Intel x64.![]()
It's exactly just the binary. That's one of the things which differenciates x64 and Arm: the format of the executable binary.
iOS doesn't run x64.
Okay, fair point. I didn't consider the development environment.Then how does the simulator on macOS Intel work?
It's exactly just the binary. That's one of the things which differenciates x64 and Arm: the format of the executable binary.
iOS doesn't run x64.
Okay, fair point. I didn't consider the development environment.
But the reverse could be applied to Windows, macOS, Android, ChromeOS: they all run on Arm.
And at this point I'm not sure what point you are actually trying to make here.
I think you have a fundamental misunderstanding here how any of this works, but I'm really in no position to give you the proper education on that topic.Binary is just binary. C++ compiles binary differently from Swift. They both run on x64.
With the Swift compiler for Windows, you can.But you can’t run a Swift app compiled for x64 on Windows.
I think you have a fundamental misunderstanding here how any of this works, but I'm really in no position to give you the proper education on that topic.
There are some great online courses on this, or maybe even YouTube videos if you are in a hurry.
With the Swift compiler for Windows, you can.
Yeah, at point you absolute made clear you don't know what I'm talking about.You’re saying:
ARM Binary = 01010010010
x64 Binary = 01010100010
And yes they’re different but they’re just binary. There’s no 2 in there.
I think this is how Rosetta 2 works by translating the binary into something executable on M1.
No, it doesn't, unless it's the most basic of programs. Because the CPU you compiled your code for is only a tiny piece of the equation. Far more important are the APIs used and available on these platforms.I suppose the point I was making is that the C++ code you write on Windows automagically works on any OS.
Are there any games that are just as amazing visually without destruction, mayhem, murder, gore, apocalyptic... LOL
Yeah, at point you absolute made clear you don't know what I'm talking about.
I don't mean the binary number system, but the executable code, generally called "binary".
Forget it. You just don't get it and this is just a waste of everyone's time. Seriously, get some education on that topic.Yes.
That has to be mapped to 0 and 1 in binary in order for the computer to run the instructions.
I suppose what I was saying is that if the computer can execute 0 and 1 on x64 for Windows, and the same x64 chip is used in macOS, then the 0 and 1 instructions should work.
But I believe ARM will not map because the chipset will not pass the instructions properly.
Mac, ChromeOS, Linux and Windows use Core i5.
There is no magic tertiary code translating the actual binary of 0 and 1.
Most non-graphic intensive games can run fine on Apple Silicon-based Macs even as ports and even through Rosetta so we don't even have to worry about them.Just no. What you think, who's gonna code for a proprietary gfx chip with a target audience not into games (or play elsewhere)?
Exaclty what happend with the PS3 and Cell. Only a few studios besides Sony could and were willing to code properly, the platform was full of bad ports, while it had a huge potential at the time and was the clear winner selling 80+ millions.
You see some similarities here?
If you're the proud owner of a new MacBook Pro, all things considered, gaming probably wasn't at the top of your priority list when you made the expensive purchase.
Forget it. You just don't get it and this is just a waste of everyone's time. Seriously, get some education on that topic.
Uh... the entire reason I want an M1 Max MBP is to game. Games run like butter on my M1 as it is, so to have that extra horsepower would be awesome.
Don't assume things.
And then realize how Apple Silicon is really just getting started. A game developer will really have no choice but to start developing native games for macOS. I also expect people who are serious about games to start taking a look at Macs (as incredible as that sounds)
Apple. tv is the “next gen console” lol..they suppose to market gaming in apple tv instead but the proc in apple tv. And not much gaming apps in apple tv.
Swift = “Hello world”
HEX (the compiled binary) = 48656c6c6f20576f726c64
Binary = 00110100 00111000 00110110 00110101 00110110 01100011 00110110 01100011 00110110 01100110 00110010 00110000 00110101 00110111 00110110 01100110 00110111 00110010 00110110 01100011 00110110 00110100
have you played ratchet and clank rift apart?Yeah...no, this is why I've got a PlayStation.