We could come to a compromise. I have nothing against multicultural 
What about ‘Swerenchenglish’? 
I think I could cope with that 
My personal take is things change… As much as being stable is important, I feel like migrating through breaking changes isn’t really that big of a deal as long as the documentation is good… and babylonJS’ documentation is great! So I feel like avoiding breaking changing until absolutely necessary would be well within reason.
Overall, my vote would be Yes, and allow breaking changes going forward IF needed. 
1 Like
I am fully aligned with the goal of improving the size and imports. Also becoming WebGPU centric is in my opinion a fair justification for breaking changes.
After all those years, I trust in the stability of the framework. A one off every 10 years is much better than most projects in our industry. If it makes Babylon better I fully support it 
4 Likes