Although there’s lots of c ‘style’ languages, the devil is always in the details/differences. I find it hard to switch between c# and js and not forget/mess up. With vb.net and js not so much a problem.
The same use to be said for vb and vbscript in days of asp From: David Burstin Sent: Tuesday, 13 October 2015 1:41 PM To: ozDotNet Subject: Re: vb.net I started my .net journey with vb.net, but these days I code C# unless I have to use vb for working with a legacy system. I agree with Bill - there really isn't much difference between using the languages in .net. In fact, knowing my way around the .net framework (from having used it with vb) made the transition to c# much easier. BUT, outside the .net world, I have found my knowledge of C# has helped me in reading (and learning) other languages - eg java, js, ruby. These all have a syntax which is far more like c# than vb. So, if you can only use one language, for me it would be C# - but there is no reason at all that you should be confined to one language. If you are interested in the job, than go for it. Whatever happens, you will learn. Any job provides an opportunity to practice our craft and become better programmers. Plus, you can do projects after hours in whatever language you want :) Cheers Dave On 13 October 2015 at 13:33, Bill McCarthy <[email protected]> wrote: This usually a great rant starter for a Friday conversation. Realistically though Vb.net is much a muchness with c# on .net. Definitely the best language if doing integrated xml. With late binding stuff it has some advantages with better conversions, but also disadvantages such as wider scope. Realistically the biggest disadvantage of vb.net is if you want to integrate some large source code from open licence stuff... usually more is available in c#. From: Tom P Sent: Tuesday, 13 October 2015 12:48 PM To: ozDotNet Subject: vb.net Guys I've been offered a junior dev job but they insist on vb.net only. Does anyone know what is happening with vb.net going forward? I would hate to get stuck into the vb.net world and have it killed off within a few years. Thanks Tom
