You don't reference self when calling a method, what on earth are you talking about? You start with the instance when calling the method, like most/all other OOP languages.
Also there are benefits with the explicit self/this to access instance properties. In C++ you need to make sure all class properties/members have a naming scheme that does not conflict with potential parameter names or other names of other variables.
The SS1 remake was amazing. But you have to remember the amount of work it takes to remake a game, SS1 was in development for many years.
SS1 really needed a remake, SS1 had awful controls and cumbersome UI, combat was also a bit fiddly.
I would say SS2 is much closer to a modern game than SS1 was, so I'm not surprised they decided to remaster it. I would also be surprised if they earned back the money they spent on that remake.
Remaking a game basically means creating an entire new game, then ensuring that it acts the exact same way as the original. The remake is most likely not written in the same game engine as the original so that means A LOT of tweaking to get gameplay, combat, triggers, event handling etc. to work the exact same as it did earlier.
I just wish people would understand how hard it is to make a game. Changing the game engine could easily set the team back 1-2 years.
Because it's a lot of work to remake a game. Besides SS2 doesn't really need a full remake.
Yeah, some weird accusations. Python has had classes since its inception (1.0).
Also the image in the post makes no sense. It shows multiple (Spidey) instances all pointing to each other which is not how self works. self is just a parameter that may contain different instances depending how it was called. This is also true for any other parameters in any function, each time a function is called it may have a different instance.