@Sirithang For AAA games, it may still work. Depends how many people will subscribe, and if in average they currently buy more than one full price game per year. For small games, not sure if it's as profitable. They'll probably keep only a few?
@Sirithang And it almost killed the premium market for games on mobile :/ When platform holders stop giving that much money, it'll be a problem. Because between Game Pass & Epic, I'll have forgotten how to buy a game.
@Sirithang May also push forward the move to GaaS, since you can still sell DLC/microtransaction on a Game Pass game. And probably with a percentage to MS even on PC, since it's Windows store?
@Sirithang For closed ecosystem, depends of the game, and can not give a fuck about it. For tools, in big ecosystem where you want sharing (company the size of Ubisoft, Unity asset store...) it's probably worth it
@Sirithang Also, for games it's often local perf, but if you allow mods ABI is important. Also tools (which is the use case in which I prefer ABI compat to debug perf, it's imported in Release by NuGet anyway)
@Sirithang Properties are functions with shorter syntax, so it's the same. And you don't need to have interface, as C# allows way more ABI compat without interfaces than C++. With allows more inlining with JIT
@Sirithang Properties allows more later structural changes in your class without breaking the ABI. If you're working on a modular project, it can be more important than Debug performance.