VB.NET and C# should continue to grow together as completely awesome examples of what the CLR can do. Don't let the haters (either inside or outside the company) dissuade you - VB is a beautiful, approachable, convenient, powerful multiparadigmatic language and Microsoft should be nothing but proud of it.
De-emphasizing VB or letting its feature set fall behind would be a huge mistake as there is a growing passionate VB community creating amazing stuff. Features like named tuple return values and pattern matching are naturals for VB. The TIOBE index has C# and VB.NET as top 10 languages with VB.NET growing in popularity. Use of either language should be a question of syntactic preference, not of capability. Co-evolving VB.NET and C# was one of the best decisions the language team ever made and with Roslyn opening up the world to .NET it is incredibly exciting to think of spinning up a Xamarin app or a Linux microservice in VB with all the goodness of a standard .NET implementation behind it. Xamarin and VB would fit like hand to glove!
The promise of the CLR is just that - a common runtime for any language. Please continue to honor both the heritage and the future of VB by keeping it strong, vibrant, and fully current.
VB is junk.....
VB is not junk and who made you king of forum posts anyway? The jerk store called and said that your delivery of jerk is ready because you're a jerk. Jerk.
I'm delivering to market a 3 year long shiny new project built on vb.net backend azure hosted with REST/JSON service, front end strict (and I mean really strict) MVVM with WPF. 60 projects total and counting. Totally OO. Entirely VB.NET.
To every VB hater out there: you don't know what you are talking about. (I already know all of the vb haters arguments so my statement is right by default:) )
To MS: continue to develop VB along with C# as there are thousands of developer who love it and are incredibly productive with it
What is the (estimated) ratio of new projects being started in VB.NET versus C#? I would be willing to bet that there are more new projects being started in F# than in VB.NET...
Twitter poll: Are more modern .NET projects started as F# or VB.NET?
Hello, i just watched channel 9 conference about .net languages and Anthony D. Green was missing. What is going on there ? What are the future plans for this language.. Xamarin ?, asp?
Please provide some information about this.
I'm not a C# hater , just more familiar with vb.
Wow. As a genuine fan of VB, C#, and especially F#, I really worry about some people.
If Microsoft can embrace Linux, bridge to iOS, and spend hundreds of millions of dollars buying Xamarin so it can GIVE it away for free to developers using Swift, Java and Objective-C to write for platforms other than Windows...
Certainly you can be open-minded and big enough to let people choose their programming languages for their own reasons without ridicule, meanness and snobbery.
VB.NET is great. I like to have F# REPL intellisense and REPL nuget integration. Thanks.
Please respect VB by bringing back its real self, ie. classic VB. VB.NET is nothing but an abomination usurping VB's name.
I wasn't there because BUILD is a wildly popular conference that's packed to the seams with people (ask the fire marshals) and we want to save as much room as possible for attendees. I didn't have a talk planned or much to contribute to some of the exhibitions on the floor so I hung back in Redmond. In hindsight I probably should have flown in just to sit in the lobby with Mads, Dustin, David, and Seth. Maybe next year :(
That said, we'll have exciting things to say about VB in this release. No worries :)
As to the budding language designer question, there really are a lot of perquisites if you want to be serious about it. You should understand Church (Lambda Calculus, simple and typed, and the reasons they were created) and Turing and a lot of the foundational things, make sure that you understand denotational and operational semantics (Scott, Strachey). A lot of the core ideas in PL are well covered in Haskell or ML (or OCAML), and a lot of the papers will use that syntax, so you probably want to understand those languages. Understand Pierce's Types and Programming Languages and Robert Harper's Practical Foundations for Programming Languages, and you really want to be able to read academic papers in Programming Language Theory. There really is a wealth of knowledge out there but it is not always easily accessible. But that is if you really want to be serious about it. You can always just do it (but you will likely recreate problems that Church solved in the '30s). There are tutorials for writing a Scheme interpreter in Haskell that would be an interesting first foray, and then implementing some of the type checkers would also get you grounded in the basics of Type Theory (I am heavily biased in typed languages direction -- correct by construction).
I wish MS would make some comment on C++/CLI. Maybe not even mentioning it in a chat titled "The future of .NET languages" is enough of a comment!!!
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.