Hi Daniel, Sjored
As I said I too think case-sensitive is better :) Now, my goal is consistency, so either change it all to case-sensitive, or the opposite makes me happy. I just want to keep the break small at the same time. You've made a good point in deprecations that I haven't taken into consideration of. Surely, deprecations exists as a way to hold the BC break as small as possible for changes, and that make sense to me. Now, given this idea, I'd lean to the case-sensitive side because deprecations make the break small enough to me, and I don't see the advantage of this current proposal. I don't want to debate about why case-sensitive is better. I'd say its quite a common view for today's developers. Or maybe I am the only one thinking that way. I will stop this proposal and add this (stop using case-insensitive extension names) to the 8.7 deprecation RFC later instead. Weilin
