Difference between c# and VB.Net
-
VB.NETis a crap,C#is a truly advanced language. They are functionally equivalent. :rolleyes:If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke
[My articles]I usually use C#. C language is more scientific than VB.net. But in some small application, VB is easier to handle.
-
J a a n s wrote:
with out any satisfactory reasons from the HR dept
That's their prerogative. If, for instance, they are interviewing lots of people then they, quite frankly, don't have to give you a reason. They are doing you the favour of interviewing you, not the other way round.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
Pete O'Hanlon wrote:
They are doing you the favour of interviewing you, not the other way round
I don't agree, in general. Unless I would be unemployed or waiting for an interview at Google, I'd have walked away. It's called mutual respect. As much as I need to market and sell myself in an interview, the same applies to the company that wants me to work there. Anything else makes big red noisy warning lamps go off in me.
Time you enjoy wasting is not wasted time - Bertrand Russel
-
Utterly stupid and biased reply. VB and C# are ALMOST identical, there are no big differences.
Which is probably why they asked the question (giving them the benefit of the doubt) as being aware of the small differences shows attention to detail at least. Saying that, I have been asked this same question more than once in interviews, but it was a few years back, when the differences were more pronounced.
-
Last weekend I went for an interview in a Reputed organization. The first question from the interview panel was the difference between VB.Net and C#. I just came back!!! Can any one here spot the differences :)
"Never put off until run time what you can do at compile time." - David Gries, in "Compiler Construction for Digital Computers", circa 1969.
VB and VB.net - allowing idiots to code for the past 20 years. JK
-
J a a n s wrote:
with out any satisfactory reasons from the HR dept
That's their prerogative. If, for instance, they are interviewing lots of people then they, quite frankly, don't have to give you a reason. They are doing you the favour of interviewing you, not the other way round.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
Sorry Jaans, thats not the way it works. The whole idea of the employer/employee relationship is one of mutual benefit. If they mess you about looking for the right person then either its already a done deal for someone else, or the company are not interested in employee relations. I would think seriously about working for a company that displays this level of rudeness, incompetence or both.
-
Last weekend I went for an interview in a Reputed organization. The first question from the interview panel was the difference between VB.Net and C#. I just came back!!! Can any one here spot the differences :)
"Never put off until run time what you can do at compile time." - David Gries, in "Compiler Construction for Digital Computers", circa 1969.
-
Actually there are at least three fundamental differences. 1. Certain functionalities are NOT exposed in VB.Net in the framework! Thereby C# is mightier ;-) 2. vb.net' "shared" key word dos not exactly behave like the static keyword in C#. I read somewhere that it has to do with the downward compatibility for old code to be portable. So VB.Net does NOT have an equivalent to the static keyword! The static keyword in C# you can trust. Shared keyword in VB.Net you can trust too but not in the same way. 3. VB.Net does not know advanced syntax like ++/-- or other short writing styles for long statements like (x=y)?a:b. In VB.Net you need to call a function IIF for such.....
Let us not forget AndAlso
-
Last weekend I went for an interview in a Reputed organization. The first question from the interview panel was the difference between VB.Net and C#. I just came back!!! Can any one here spot the differences :)
"Never put off until run time what you can do at compile time." - David Gries, in "Compiler Construction for Digital Computers", circa 1969.
The real trick is answering a question like that with one word. Syntax.
-
VB and VB.net - allowing idiots to code for the past 20 years. JK
Very True. C# has only allowed idiots to make code for that last 7 years.
-
Marcus_Idle wrote:
asked a fairly open question
My discussion was scheduled at 9:30 AM, and was done at 1:30 PM, till then I had to wait there, with out any satisfactory reasons from the HR dept. I was so frustrated when I went to the panel. Listening to the first question from the panel made me think otherwise.
"Never put off until run time what you can do at compile time." - David Gries, in "Compiler Construction for Digital Computers", circa 1969.
4 hours is nothing. This is a strategy I may encourage to my employer, to weed out people who don't actually want a job. Or who are to self important.. I waited for 2 hours on a conference call for a client .. 3 work days ago. One of the things that makes an organization respectable is that they WILL WAIT .. PATIENTLY for a client, and not get flustered or become RUDE when that client has the time to interact with the company. Your attitude would not have made it past the interviewing process of my employer.
I'd blame it on the Brain farts.. But let's be honest, it really is more like a Methane factory between my ears some days then it is anything else...
-
J a a n s wrote:
with out any satisfactory reasons from the HR dept
That's their prerogative. If, for instance, they are interviewing lots of people then they, quite frankly, don't have to give you a reason. They are doing you the favour of interviewing you, not the other way round.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
Pete O'Hanlon wrote:
They are doing you the favour of interviewing you, not the other way round.
I completely disagree. I have never, and never will, grovel for a job. My employers have ALWAYS understood that I was doing them as big a favor letting them use my talent as they were doing for me by willing to do business with me. You will be better paid and better respected if you keep that frame-of-mind in an interview instead of carrying the "please hire me" attitude. The latter is a loser's mentality. -Max
-
Last weekend I went for an interview in a Reputed organization. The first question from the interview panel was the difference between VB.Net and C#. I just came back!!! Can any one here spot the differences :)
"Never put off until run time what you can do at compile time." - David Gries, in "Compiler Construction for Digital Computers", circa 1969.
C# more closely resembles a real programming language. The keyword being "resembles". ;P
-
Last weekend I went for an interview in a Reputed organization. The first question from the interview panel was the difference between VB.Net and C#. I just came back!!! Can any one here spot the differences :)
"Never put off until run time what you can do at compile time." - David Gries, in "Compiler Construction for Digital Computers", circa 1969.
You can accomplish pretty much the same thing with both. I use 'em both. I prefer C# now for new code, but I don't mind maintaining our huge code base written in VB.Net either. They both compile to IL and get the job done. This is a really old topic, though not as old as the silly "Linux vs. Windows" one is! -Max ;-)
-
4 hours is nothing. This is a strategy I may encourage to my employer, to weed out people who don't actually want a job. Or who are to self important.. I waited for 2 hours on a conference call for a client .. 3 work days ago. One of the things that makes an organization respectable is that they WILL WAIT .. PATIENTLY for a client, and not get flustered or become RUDE when that client has the time to interact with the company. Your attitude would not have made it past the interviewing process of my employer.
I'd blame it on the Brain farts.. But let's be honest, it really is more like a Methane factory between my ears some days then it is anything else...
-
Sure, because everyone wins when you only hire the desperate and those with no self-esteem. I shudder to think of what level of talent you must have in your organization. Do you motivate with whips as well?
Patience is a virtue. How well would this guy represent your company when he is sent out to do an onsite demo, and the client has.. for any reason needed to put him off until they have their ducks in a row.. will he go in there all huffy and hostile? or will he go in there and be understanding... I personally wouldn't want to work for a company who would have an employee who is so self righteous that he/she couldn't be bothered to sit patiently until an internal matter had been taken care of. And yes we have whips but they are only for the self righteous and those that never make mistakes. :-\
I'd blame it on the Brain farts.. But let's be honest, it really is more like a Methane factory between my ears some days then it is anything else...
-
Patience is a virtue. How well would this guy represent your company when he is sent out to do an onsite demo, and the client has.. for any reason needed to put him off until they have their ducks in a row.. will he go in there all huffy and hostile? or will he go in there and be understanding... I personally wouldn't want to work for a company who would have an employee who is so self righteous that he/she couldn't be bothered to sit patiently until an internal matter had been taken care of. And yes we have whips but they are only for the self righteous and those that never make mistakes. :-\
I'd blame it on the Brain farts.. But let's be honest, it really is more like a Methane factory between my ears some days then it is anything else...
That's quite different than just making a guy sit and wait for no reason. If there's a scheduling problem, or an emergency comes up, sure. I'd wait. But if the company just has a policy of letting an interviewee sit for hours just to see if he/she will, that's BS. If it works for you, then great. I can pretty much guarantee I'll never work for you.
-
I agree in general. But I personally have experience, knowledge and good interview technique. Therefore its always a hiree's market. If a company is after a candidate who is willing to wait 4 hrs without ecxplaination, they're not after me.
I read a great article the other week that talked about developers' ego and how the only truly common belief among us is that "I am smarter/better than everyone else". This seems to be a mix of that and pure perspective. Someone hiring wants to believe they can hire anyone and that they're doing you a service by interviewing you. Someone looking tends to believe that they are somehow better than every other candidate out there and therefore you'd be lucky to hire them. It's a two way process and neither party will be happy or productive unless both parties are both interviewers and interviewees.
-
J4amieC wrote:
I can take any job I please, they are looking for 1 individual. Therefore Im doing them the favour of offering my services, if they don't cut the mustard (and that includes shoddy interview/working practices) I hit the door and walk into the next interview.
In a strong employment market, this is the case. The reality, at the moment, is that I don't need to hire you - there are a lot of others who would be willing to take the job. It's a hirers market at the moment and if you need a job, you can't afford to be that choosy; unless you fancy flipping burgers.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
It's not a matter of a strong market for employers or employees, it is about courtesy. If the reality is that you don't need to hire them, then it is a real waste of the candidate's time to be there when they could be pursuing a viable position. Taking advantage of a market is one thing, but a person is another matter. Because you feel you can do without them or they need you more than you need them speaks very poorly of you not the candidate. If you are discourteous to the candidate, would you feel snubbed if they just got up and walked out? If you are looking for people to kowtow to you, then shame on you.
slartybardfast, but not too fast.
-
J4amieC wrote:
I can take any job I please, they are looking for 1 individual. Therefore Im doing them the favour of offering my services, if they don't cut the mustard (and that includes shoddy interview/working practices) I hit the door and walk into the next interview.
In a strong employment market, this is the case. The reality, at the moment, is that I don't need to hire you - there are a lot of others who would be willing to take the job. It's a hirers market at the moment and if you need a job, you can't afford to be that choosy; unless you fancy flipping burgers.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
It doesn't speak well for you or your organization if you think developers are interchangeable regardless of economic conditions. Organizations that have that attitude always end up with a statistically impressive set of third rate programmers. That's because the good ones get tired of not being valued, watching inferior ideas win, etc, and easily can move on, while mediocre programmers eventually realize that they've finally found a job that won't weed them out. This process accelerates until all you have is mediocre programmers that know they suck and count themselves lucky to have a job, and inferior programmers that have yet to figure that out. The only way good programmers come in is via new hires. In other words, by accident, and they leave once they wise up.
-
Pete O'Hanlon wrote:
They are doing you the favour of interviewing you, not the other way round.
I completely disagree. I have never, and never will, grovel for a job. My employers have ALWAYS understood that I was doing them as big a favor letting them use my talent as they were doing for me by willing to do business with me. You will be better paid and better respected if you keep that frame-of-mind in an interview instead of carrying the "please hire me" attitude. The latter is a loser's mentality. -Max
Exactly. It is better to be the oppressor than to be the oppressed!