A Response to DonXML's "XLINQ XML Literals... Classic ASP Spaghetti Hell? "

[I started this as a comment on Don's blog and decided it was getting too lengthy for a comment]

Don,

[Let me switch on my Religion Degree Hat... Unnhhh... Ok... I think it's on... do you see the light??  No... Nuts...  Ahhh... the switch... bzzzt!]

AMEN!!!!!!!!! 
In the past this type of post would have gotten my dander up a little, but (in case you haven't noticed), my first project over at ASPSOFT is a C# one.  I still am somewhat passionate about VB, but mainly because I recognize it as the entrance to professional programming.  As Phil Haack said we need to expect more of Mort -- and all professional developers!! (In essence you're talking about Mort too).  I know that the lure of the VB team is to make it easier.  I would implore the VB Team to make it easier for us to write good code better. 

As far as C# goes (I have been meaning to state this to the world)
No sweat!  If you can write bad code in VB (like me); you can screw up C# too <grin />.  Honestly I made the jump with no effort; I'm quite amazed.  Evidently I knew C#... I've noticed that over the last several months I have looked at .Net Code (C# and VB.Net), and haven't really realized that I was looking at C# or VB code... it was just .Net code... Pretty cool!  I'm liking the C# thing... Maybe I'll stay over on the C# side and pollute the pool <grin /> 

With that said...
ATTN MS!  I demand that you give us C#ers some of the productivity enhancements you gave the VB guys.  Specifically I want Default Windows Forms Instances!  I want to design a Windows Form with the designer and only have to write "form1.show();"

[In case you missed it that was sarcasm]

Print | posted on Tuesday, February 07, 2006 11:02 PM

Feedback

# re: A Response to DonXML's &amp;amp;quot;XLINQ XML Literals... Classic ASP Spaghetti Hell? &amp;amp;quot;

left by at 2/8/2006 1:17 AM Gravatar

Welcome to the Dark Side, Jay. Your official pair of curly-brace underwear is in the mail :)

# re: A Response to DonXML's &amp;amp;quot;XLINQ XML Literals... Classic ASP Spaghetti Hell? &amp;amp;quot;

left by at 2/8/2006 9:39 AM Gravatar

I think it's a tradeoff. VB.NET and C# both can do the same thing more or less, so choosing one over the other has no real advantage. To make that more clear, you have to make distinctions, so one can do things the other can't (or better: it's harder with the other) and vice versa. This has the big advantage that you don't have to compromize language A because language B is designed by people who don't think it's worth the effort.

I'm glad MS finally made the decision to give VB.NET and C# different directions, even though it will include more work for people like me who have to write code for both.

Others disagree with the decision and want both languages to be equal, which IMHO is silly, because you then can better merge the teams and drop 1 language so more stuff can be done.

Title  
Name
Email (never displayed)
Url
Comments   
Please add 6 and 5 and type the answer here: