Well there's my thoughts. Looking forward to learning more python and hopefully a bit of C++ in the new year

For the particle system, it felt like iterating over things was quite slow. It took quite a lot of work for me to understand displayables in Ren'Py too. Needless to say my particle system is not very performant. I'd quite like to try a compute shader system again for lots of particles

Something that really got me was how python manages instances of objects - for ages every emitter I created in my particle system shared its list of particle objects. When I initialised the list() in the emitter constructor this problem went away. Not sure why

Positional and keyword arguments felt new to me, once I understood them I started to understand the error messages I kept getting. Quite handy actually being able to specify which variables you want to set

Python doesn't do function or constructor overloading, to get around this I used default values in the function/class declaration

I'm so used to the way C++ manages scope and variable lifetime. Python does not work like C++ here!! As far as I understand it, every variable is kind of global, except in certain circumstances like functions which do introduce scope

Also took ages to get used to the tabs thing, as well as not needing semicolons. However, on coming back to writing C++ I'm finding myself missing out semicolons all the time, so maybe I kind of like it?? I miss being able to easily spread things over multiple lines for readability though

Python feels like it's not meant to be used with classes and member functions. It took me ages to understand that "self" has to be passed as an argument to a member function