Ah, I may have misunderstood the intent behind some of your wording, my bad.
The whole issue does make me hope open standards continue to gain more adoption. One can hope, right?
Anyway, again, my apologies - it does sound like we’re kinda on the same page here after all.
Whoah, no need to get defensive! That was just a guess based on my own observations, and I never said anything about whether they have the right to do whatever the hell they want with their own chips (which would be true regardless, I reckon).
That said, given that their business model depends on their walled garden approach, I just find myself wondering if they might’ve seen the possibility of running any old ARM executable on their silicon as a potential threat to their business model? But there’s all sorts of factors in play, so maybe I’m wrong and that whole possibility is irrelevant.
Do you happen to know if they strictly extended existing APIs?
That will only work if executables compiled with ARM as the target can run on Apple silicon. My understanding was that even though they used ARM as the basis they made significant changes to the instruction set, which would require being able to compile targeting the M1/M2 chips.
I’m not 100%, but I suspect this will be a problem…
deleted by creator
I tried it and found it kinda…obtuse? I found it far more confusing than Heroic, so really saw no advantage to switching.
And hell no on the subscription model if that’s the route they went with. Not to mention kinda seems doomed to fail when it’s competing with a Foss alternative.
Hard pass from me.
Hmmm, I wonder if Valve might, quite accidentally, end up turning SteamOS into a viable option. Immutable, flatpak app store, simple install, etc. But desktop mode would need a lot of work, so…maybe not.
But it would be funny as hell if it happens!
Heh. Yes they’re similar, but on the technical side different in a very important way. It has to do with opening a file from inside another program. If you select a shortcut, the program with treat or as a separate file, so most of the time the action will fail. A link, though, you should end up with the program opening the target of the link. In other words, a shortcut is a file that points at a different file, where a symlink involves she filesystem trickery to accomplish almost the same thing.
That’s a horrible, just terrible explanation, though - but I’m pretty sure this is the gist of it.