In my opinion it's not important what C# naming convention you use, but it's important to be consistent. Consistent in the sense that you use one naming convention for the entire API. Right now, I found three different naming conventions in Unitys API: The old naming convention everybody knows by now .NET standard conventions, see here "Shader programming like everything in lower case" convention, see here I would very much prefer if you can stick to one naming convention only. I understand if you want to transition to another naming convention. It means we have to deal with two different naming conventions for a couple of years. Not ideal, but I understand the idea behind it. What I don't understand is, and believe you don't do yourself a favor by doing that, to add more than two different naming conventions. It's going to make the transition for you even harder. I also do understand your intention with the new math library to make it easier for shader programmers to write C# math code. But overall, you write C# math code and it should feel like a first class citizen in C# land.