XAML case sensitivity.Reloaded.

Rob Relyea, the program manager for WPF & Xaml Language Teams, responded to my post in which i complained about the fact that XAML is case sensitive. Here are some facts : - the WPF API will be CLS compliant ( so it can be used from case insensitive languages like VB.NET) . So the XAML case sensitivity can't be forced by the API (the Button class , for instance, can't have 2 properties named "Content" and "content")
- the purpose of XAML, as a text based high level markup language is, to be used from multiple content providers (developer and designer tools, hand written etc) and to be easily created/modified (that's why it text based instead of a binary format). That's why the tools don't spit BAML but XAML.
So, with all these, why make it case sensitive ? It will only make it harder to modify it manually. I'm sure VS Orcas will have a good XAML editor. But you know what.....to make a small change to a HTML file i don't use Visual Studio. I use the "instant load" Notepad++ editor. That's how i was expecting to edit XAML too.....with Notepad++. Case sensitivy hurts a lot this "quick edit" scenario.