I finally completed the brush-up of the articles I wrote over the last 10 years! With this 🧵, I am going to present them 1 by 1 as they will be worthy of attention for a while. This exercise has been cathartic for me and I hope it can deserve your RT or share.
An introduction to the issues that an IoC container could solve. The article was written when I made (and then later on abandoned) Svelto.IoC. The article has a good explanation of the Singleton and Unity limits.
You showed an interest in knowing why I currently think the ECS paradigm can be used to write maintainable code. This is going to be a long read (20+ tweets) but it's a summary of what I write on sebaslab.com. Let me know if it makes sense to you:
In case you never used a procedural language: have you ever thought how to write a whole game with it? It was fun. A main function was usually running a single loop for the duration of the game execution with all the logic in it, laid out sequentially
