|
can't vouch for the authenticity[^] 
Once you lose your pride the rest is easy.
In the end, only three things matter: how much you loved, how gently you lived, and how gracefully you let go of things not meant for you. – Buddha
|
|
|
|
|
|
Richard Deeming wrote: ...obviously have no taste-buds.
Maybe, will see.
Putting it on my Things To Try While In Wales to-do list.
Sometime in the near future 
|
|
|
|
|
Appologize if this is childish question but i am in too much confusion.
I learnt first language vb6.0 in 2008 then i was student later and i continue it many years then 2 years ago i shifted to vb.net but in markete there is demand of c#. Many peoples told that c# is better than vb.net that,s why there is no value of vb.net in markete. I still can,t find any job to work in vb.net while i know vb well. Then i learnt C++ and i learnt it well and then i moved to c# and now i can code in c#.
But problem is that i can,t code in c# same as in vb.net. I mean i always prefer vb. In vb i can solve any problem. but in c# i have to search from start and i don,t know why i like vb.net too much. In other words i don,t want to leave vb but markete always force to work in c# and foget vb. If vb is too bad in markete then why microsoft still supports it. Microsoft must close vb because they can,t give good markete to vb. Due to this reasons vb only developers are still poor in markete. They can switch to c# easly but their hearts shall always stick with vb.
I know many languages like vb,c#,java,asp.net,php,mysql,sql etc but my heart always stick with vb. When i code in other language except vb then i always think to do that task in vb also.
I love vb but what should i do while markete don,t have demand of vb?
|
|
|
|
|
Learn how to say "would you like fries with that?".
|
|
|
|
|
+5 
Jeremy Falcon
|
|
|
|
|
What you mean please mention in details i am interested in your kind answer.
|
|
|
|
|
This is an expression used in the US (possibly elsewhere) for someone who has to work in the fast food industry (like McDonald's, Burger King, etc), usually because of their educational choices.
It's from a joke that tells what certain degreed people say in their job each day (see here[^]).
So he's basically saying, learn another language or be forced to take a minimum wage job.
I think the advice given by Daniel Pfeffer below is great: Use the language that pays for your work and use the language you love for personal projects.
|
|
|
|
|
There are places that use VB.NET. I would imagine there are enough licenses sold that Microsoft feels it is worth while.
Keep practicing your c# and it will come easier for you.
Good luck.
Mongo: Mongo only pawn... in game of life.
|
|
|
|
|
Yes you are right with passing time i am feeling c# is becoming easy for me but in heart i still prefer vb too much upon c#.
|
|
|
|
|
Short answer - suck it up.
VB has a bad reputation, a lot of it deserved. I worked with VB from conception on early Windows through to VB6 and started moving into VB.Net bey never transferred. C# and VB.Net compile to the same runtime and AFAIK most of not all commands are convertable 1:1. A lot of people won't accept that the two are in the same ecosystem but you can chose - stay with what you know or move on.
In my career, I started in COBOL and moved through various other languages - including C, VB and Java - and I now find myself as a newbee with all the web tech. The answer is not to moan, but to knuckle down and learn the new stuff.
veni bibi saltavi
|
|
|
|
|
Bro!
You are absolutely right. There are many commands in vb which can,t be converted in C# but most people don,t accept this reality.
I am also feeling myself a newbie and worrying about it. I never think i can,t do something in programming but when i look to markete then this reality comes that vb don,t have demand.
With passing time while i am practicing c# i am found that it is realy becoming easy for but in heart i still prefer vb upon c#.
|
|
|
|
|
Member 9993589 wrote: Bro!
... and I stopped reading.
veni bibi saltavi
|
|
|
|
|
Using the word "Bro" I showed respect for you. but i can,t understand why you stopped reading... have i done something wrong which you don,t like?
|
|
|
|
|
Yeah, I have seen this discussed from time to time. For Microsoft, VB.net carries almost no expense as they do not have to maintain a separate compiler. Visual Studio just translates both C# and VB.net into the intermediate language (CIL?) which then gets compiled. (Actually I have heard C# described as C++ with VB goodness baked inside).
Interestingly, according to TIOBE this month VB.net ranks #7, between Python at #6 and PHP at #8. Even Visual Basic (VB6?) ranks at #11 just above Perl.
There are a lot of prejudices out there. I have noticed hard-core C programmers tend to look down their noses at C++ and C# folks. Then again Assembler programmers tend to look down on all the Compiler folks (C included), who in turn tend to look down on folks using Interpreted languages. Then again I am sure that 50 years ago there were folks entering programs on the register switches in front of computers back then who thought the Assembler folks were clots (I did this once, no great fun tho).
In short, Member 9993589, welcome to programming!
|
|
|
|
|
Despite all the "holy wars" regarding the best language, for most projects the choice of language is arbitrary. Possible exceptions are projects where access to the hardware is essential, or there are hard real-time or memory requirements.
Most of us don't have the luxury of programming in the language that we love most. This may be because the legacy code was written in a different language, because of contractual requirements, or even because your boss prefers a different language.
I suggest that you learn whatever languages can keep you employed, and develop any personal projects in the language you love.
Good luck!
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
Member 9993589 wrote: vb only developers ... can switch to c# easly [sic] but their hearts shall always stick with vb ... I love vb
I was tempted to mark this as abuse. 
Once you lose your pride the rest is easy.
In the end, only three things matter: how much you loved, how gently you lived, and how gracefully you let go of things not meant for you. – Buddha
|
|
|
|
|
"I was tempted to mark this as abuse. Big Grin | "
Looking funy
|
|
|
|
|
Anything you can do in C# you can do in VB.
But...it doesn't work the other way round: and for that I'm truly glad. VB is a very old language which was designed to be used by non-programmers, and it retains some of that to this day. Most of the stuff you can do in VB that you can't in C# improves the quality of code and the ease of maintenance. String typing rather than weak typing is the major plus here, but any language which retains "On Error Resume Next" should be recycled as firelighters... 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
OriginalGriff wrote: Anything you can do in C# you can do in VB.
Unsafe code? 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
All VB code is unsafe! 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
OriginalGriff wrote: Most of the stuff you can do in VB that you can't in C# improves the quality of code and the ease of maintenance. String typing rather than weak typing is the major plus here
I'll just mention dynamic then.
OriginalGriff wrote: On Error Resume Next
Ever seen an empty catch?
Don't blame crappy programming on the language.
Basic was originally pushed as a beginners language, but after all the bashing all beginners nowadays learn Java or C#.
Take another good look at Q&A some time. I'd say there are more stupid questions regarding C# than VB.Net nowadays.
Not to mention JavaScript. 
|
|
|
|
|
Jörgen Andersson wrote: I'll just mention dynamic then
Please, don't. var was bad enough, but at least it has a need - Linq won't work without it. dynamic is a retrograde step IMO.
Jörgen Andersson wrote: Ever seen an empty catch?
On Error Resume Next is like an invisible empty catch block round every single line of code...empty catch is bad enough, but when you can't even see them?
Jörgen Andersson wrote: Don't blame crappy programming on the language.
I don't: you can write cr@p code in any language and (with a bit of work sometimes) you can write excellent code in every language. But some languages encourage good code, by making it harder to make mistakes. And some languages encourage cr@p code by making it harder to do things properly!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
OriginalGriff wrote: var was bad enough, but at least it has a need - Linq won't work without it
Really?
I'm not having a good enough understanding of the plumbing behind Linq to be able to say you're wrong, but you can always select real types instead of anonymous types if you want to.
But yeah, the freaks that are known as linq to SQL spit and Linq to XML might be a different story.
OriginalGriff wrote: Error Resume Next is like an invisible empty catch block
It's rather quite visible.
The problem is rather, that actually handling errors in old VB was even worse. Just taste the syntax "On Error Goto ...", yes it says GOTO 
I don't understand the need to always be backward compatible.
|
|
|
|
|
Afraid so - Linq works by creating anonymous types which are specific to the query - so if you don't have a "define this from context" variable type it can't do things like this:
var v = myCollection.Where(w => w.ID < 10).Select(s => new {ID = s.ID, Name = s.Name});Because you can't declare
IEnumerable<WhatNameWillTheCompilerGiveThatDamnThing> v = ...
It only annoys me when people use it as a shortcut datatype:
var v = 123; Or to be really annoying
var v = GetSomething(somethingElse); because it may save you 5 seconds typing, but I'm going to have to hunt down the method declaration to try and work out the heck you are doing... 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
