A song for the lovers

I’m not mad, I’m talking about the custom My namespace that will be here with the .Net next shipment. Before getting into deep I want to spend two or three words about what My is and what it’s all about. First, I’m not a VB developer (I’ve basically never wrote more than 10 lines of code of VB one to six or .NET in my own life); second: My seems a toy idea but it’s only RADness. Take a bunch of “common functionalities” and collapse them under a single namespace (with a stupid name to be honest ), what do you get? My, of course

The point is not if My is useful or not, the point is: My should be only for VBers or for every inhabitant of the .NET framework? My opinion is that I could use it if they allow me to port it on Mono too (to be read: cross platform and not in unportable dlls), it makes no sense to develop a simple application gaining benefits from My and the day I try to recompile it on my Linux box have to rewrap all the code in My in a custom class or namespace or what is…

I had a discussion with Corrado Cavalli (a .NET MVP here in Italy) about a post he made and I think that mine point of view is not so wrong…

ps. please change that ugly and possessive My