Printable View
I know polls come and go, but just to see how the developers are currently going about with their programming environment, which do you use?
I know i personally am trying to get my head around VB.NET but all the code changes and control changes make it just that little bit harder.
I see no poll option for "VB sucks, I moved to a better language"
:(
I like C# alot more than VB, VB actually pisses me off.
When .NET came I got angry and moved over to C++, only using VB now for small tasks or to help out people on this forum....
Hmmm, makes ya think. We are all gonna have to move sooner or later I spose, pitty it's such a long road to do it.
I have never tried very hard to move over to VB.Net but as long as so much of the code has been altered then it is more or less just as easy to move to an other language then to move to VB.Net..
what is C# exactly?
A languageQuote:
Originally posted by mastermind94
what is C# exactly?
I thought C# was just to distinguish between C+ and C++. So C(Number). How do you pronounce C++ anyway, like:
C Plus Plus?
There is no such thing as C+. Microsoft made the C# language, ask them. C++ is pronounced as you said it.Quote:
Originally posted by Madboy
I thought C# was just to distinguish between C+ and C++. So C(Number). How do you pronounce C++ anyway, like:
C Plus Plus?
Im sure ive heard of C+, or is C# pronounced as:
C
:confused:
C# is pronounced as it is written, C-SharpQuote:
Originally posted by Madboy
Im sure ive heard of C+, or is C# pronounced as:
C
:confused:
C != C#
The more languages you know the easier it is to learn another.
Atleast for me.
Still using VB6, moving to .NET
Can't I vote for two? :9
That's a grossly opinionated statement, considering VB and C# share the same framework.Quote:
Originally posted by kasracer
I see no poll option for "VB sucks, I moved to a better language"
:(
I like C# alot more than VB, VB actually pisses me off.
Unless you got frustrated writing hardware drivers (which you wouldn't use C# for anyway), there's no real frustration between the two.
Any solid .Net programmer would know how to use both.
The syntax is different. Personally, I can't stand Basic syntax.
Du'hQuote:
Originally posted by nemaroller
That's a grossly opinionated statement
I don't see how this would have any relavence in your arguement (whatever the hell it may be).Quote:
Originally posted by nemaroller
considering VB and C# share the same framework.
What idiot would write drivers with a .NET language? Honestly now....Quote:
Originally posted by nemaroller
Unless you got frustrated writing hardware drivers (which you wouldn't use C# for anyway), there's no real frustration between the two.
There is quite a large difference between the 2 languages and, according to alot of benchmarks, C# executes much quicker in many different aspects and is usually twice as fast, or faster than VB.NET in IO functions.
Probably.Quote:
Originally posted by nemaroller
Any solid .Net programmer would know how to use both.
As CornedBee said, I cannot stand basic syntax.
whats wrong with BASIC syntax? Its like plain english compare to C++:p
Yeah, plain English is unfortunatly unsuited for programming. :p
But isnt it less of a chore to the programmer as he/she can read it? (but then again you should be able to read it if you coded it:rolleyes: )
No, C-like syntax is far more precise, once you get used to it.
Having said that, VB wasnt english looking to me when i started about 9 months ago:eek:
Is the VB language presented as Spanish, Chinese etc based on your country? Does it support other languages, imagine learning VB in english then going to learn VB in Chinese:o
Where are you aiming at?
I use both, and I while C# (JAVA) syntax is smaller and appears tighter, the differences between the two are trivial.
I think its truly a matter of opinion.
Try{
}
vs.
Try
End Try
And C# isn't faster in IO functions. I know there was a thread in here where we discussed this using a certain piece of code, and Edneesis had trimmed it from 4x faster in C# to 2x faster in C#.
But one block of code doesn't make a valid case. In fact, I'd be willing that code was run with Integer array bounds enforced in VB, which slowed it down.
No it's not....why do you think there is so many forreigns at this forum...;)Quote:
Originally posted by Madboy
Having said that, VB wasnt english looking to me when i started about 9 months ago:eek:
Is the VB language presented as Spanish, Chinese etc based on your country? Does it support other languages, imagine learning VB in english then going to learn VB in Chinese:o
Actually, it is. There are many different benchmarks for this proving it is true, not just that one thread. There was also an article about C#'s speed versus VB.NET's speed on the MSDN, good luck finding it though (Microsoft has made THE worst search engine for the MSDN).Quote:
Originally posted by nemaroller
And C# isn't faster in IO functions.
Bah.. as much as I want to learn c..
1. I havent exactly 'mastered' vb as well as i would like to first :blush:
2. I have no idea where i'd start learning C++.. as i sort of stumbled upon Vb :(
Get a book...and/or start to read CornedBees tutorials..:D
I haven't seen any articles on the differences between IO functions. The ones I have seen are comparing C# using the framework IO functions against VB using the VisualBasic.Compatibility file functions (related to the VB6 friendly (VisualBasic Namespace commands), instead of VB with the framework IO functions... and they conclude by saying, use the .Net IO functions (well duh).Quote:
Originally posted by kasracer
Actually, it is. There are many different benchmarks for this proving it is true, not just that one thread. There was also an article about C#'s speed versus VB.NET's speed on the MSDN, good luck finding it though (Microsoft has made THE worst search engine for the MSDN).
VB does suffer from 'over-boxing', but option strict enforcement and just good programming reduces it (although it may be far too easy to accidently do in VB), and the bottom line here is the Whidbey release (w. next .Net framework version) will attend to the poorer reflection performance in VB.
Like the thread in this forum, Edneesis stated that the VB test was run with Integer overflow checking on, which may have attributed to the results.
And, supposedly, edit-and-continue functionality will appear in the next IDE... along with pointers in the next framework v. Until then, people that care that much, can implement marshalling:
http://www.dotnetbips.com/displayarticle.aspx?id=229
Quote:
Originally posted by nemaroller
Like the thread in this forum, Edneesis stated that the VB test was run with Integer overflow checking on, which may have attributed to the results.
If you are using VB and you are not making databases you should never use Integers anyway...
Well, I'm still out on that.
With 64Bit processors on the way, Integer may in a few years map to a 64bit type and be the best format for a 64bit processor. If I explicity declare any integer as int32, then what performace problems may that cause?
Definitely for working with the API, declaring int32 is imperative. But for the majority of my work (databases), or even using integers as iterators, I'm still using Dim X As Integer (vs Dim X as Int32).
If you have any additional insights, I'd love to hear em.
Quote:
Originally posted by nemaroller
Well, I'm still out on that.
With 64Bit processors on the way, Integer may in a few years map to a 64bit type and be the best format for a 64bit processor. If I explicity declare any integer as int32, then what performace problems may that cause?
Definitely for working with the API, declaring int32 is imperative. But for the majority of my work (databases), or even using integers as iterators, I'm still using Dim X As Integer (vs Dim X as Int32).
If you have any additional insights, I'd love to hear em.
I am talking about VB4-6 not .NET....where Long should be used in stead of Integer. And when 64 bit prosessors takes over the market there will probably be optimised compilers for that too...
what about Delphi :p
Oh.. :) Well, the test code I was referring to was written in .Net.Quote:
Originally posted by NoteMe
I am talking about VB4-6 not .NET....where Long should be used in stead of Integer. And when 64 bit prosessors takes over the market there will probably be optimised compilers for that too...
As long as the variable is 32bits long, it's faster then the original 16bit integer in VB6....;)
The Athlon64, at least, shouldn't have any noticeable speed disadvantages for 32-bit integers vs. 64-bit integers - but I might soon be able to test this ;)
I'm currently torn between VB and VB.net.
VB6 is better for writing quick programs whereas it takes me about 3 times as long in .net. but VB.net is so much more versatile than vb6.
Plus, IMO drawing operations were so much easier to understand in vb6.
It was perfect so they went and improved it :(
I have heard that it is actually a bit faster on 32bit integers too..Not that I understand why....Quote:
Originally posted by CornedBee
The Athlon64, at least, shouldn't have any noticeable speed disadvantages for 32-bit integers vs. 64-bit integers - but I might soon be able to test this ;)
BTW can you buy one for me too...
Mine's already lying around in my room, but the mobo hasn't arrived yet.
I am soo jalous of your new girl CornedBee. Even if I don't need a faster PC for what I am using it for at the moment. But it always nice to have a new girl tight girl. What MB and CPU have you bougt? How fast? And what RAM?
I was programming in VB6 for about 3 years .
Moved to VB.NET for 2 years now .
Moved to C#.NET for about 6 months now .
I hate both VB & VB.NET . Both suck , both stupid . C# synatx is really lovely and I agree it's more precise like C/C++ .
Where's the option for those of us who use both?
If I make something that I'm going to send to people or distribute, I'll use VB6. But for educational purposes and dicking around, I'll use VB.Net.
So which should I vote for?
If I understand correctly, the Integer type in VB.Net could be mapped to 64bit or whatever in the future, depending on the .Net framework version. So a variable declared as Integer in v1.1 would map to 32bits, where as in v1.2, it could easily be 64bits, the framework of that future time reflecting the most optimal (native) length for the processor of the day.Quote:
Originally posted by NoteMe
As long as the variable is 32bits long, it's faster then the original 16bit integer in VB6....;)
The code you write doesn't change, but the underlying memory space will. Which is why most people strongly suggest using Int32 for working with the API. Then again, how long is the WinAPI going to be with us now that Longhorn is on the way. I don't have any Longhorn beta so I'm just speculating on this part.
If MS removes the API, 99% of the current applications will stop working. Sounds like a good business decision ;)
Athlon 64 3200 (2 GHz I think)
1 GB RAM
Some Asus Mobo
Sapphire Atlantis Radeon 9800 Pro 128 MB
Then it isn't that much fater then what I have. But I still want a 64 bit prosessor.....