Printable View
Thats correct but while there is still an open source linux community c++ will remain and while people still want quickly deployed applications VB will remain.Quote:
Originally Posted by John_420
Its all about the right tool for the Job and no one language will ever have total dominance
Absolutely!Quote:
Originally Posted by Pino
We observe that many programmers, often novices, seem to have the mindset that one can only use one language, and that using another involves 'quitting' the previous. Why is this?
Some facts:
— All programming requires a constant core skill-set: logical analysis, problem solving, and so on. These attributes will always be required and will never change because they are fundamental to computer science.
— Applying computer science theory also requires practical knowledge; one can pick this up from using any programming language, but most of all from using a diverse set of them — working with different paradigms, and understanding the need for each.
— Finally, there are skills in individual languages. These skills are the most highly sought after, but the least valuable of all.
Why? Because anyone who understands the fundamentals of programming can pick these up as they are required.
There are always a few languages which are in vogue; skills in these will make you more employable at the present time. C# and Ruby are a couple of current examples. C and C++ jobs tend to be fewer and harder to find, but C and C++ programmers are generally considered employable forever, simply because those languages are mainstays of the industry. Other languages come and go, unless they are very specialised (FORTRAN, Lisp, APL come to mind).
But it is the understanding of programming itself that is the most valuable attribute of all.
That is probably the sanest, well-reasoned posting I've seen in the VB6/.NET/C(++/.#) debates I have ever seen.
-tg
This post is way, way off topic.Quote:
Originally Posted by John_420
This thread is all about an important issue that we are all about to navigate.
That's the change in VB6 to .Net programming positions, jobs and opportunities and how we successfully move through this.
This applies to programmers and those of us who run shops ourselves.
Opinions on MS and C don't apply. There are many other threads talking about this - although they seem to get locked after a while...
I would agree. While C# is a nice language, it's meant to be a RAD language for developers who want a little more control as opposed to VB (since C# can use things like unsafe pointers).Quote:
Originally Posted by Pino
C++ is meant for high performance and system development. You'll never see C# on an embedded device or in a performance critical system / application.
Since DirectX is written in C and C++, C# calling it isn't much more expensive than C/C++ so I wouldn't be surprised if we start seeing a few more games being created in C# but you won't be able to do that in a cross-platform way (i.e. on different consoles other than the XBox 360 or OS X). C++ will still be primarily used in game development for this reason alone.
Well I would agree and disagree on this point. F# seems new and interesting as a functional language but J# was total garbage. Though I would agree with szlamany that this is off topic.Quote:
Originally Posted by John_420
Mr Obvious. We somehow got drifted but you posted that is even more off topic. Yes MS and C# do apply because you said yourself that this topic is about Jobs and other positions. Now i like to think MS employing people is on topic, and C# programmers are replacing jobs of VB6 and .NET. So Programmers wanted by MS is on topic.Code:This post is way, way off topic.
This thread is all about an important issue that we are all about to navigate.
That's the change in VB6 to .Net programming positions, jobs and opportunities and how we successfully move through this.
This applies to programmers and those of us who run shops ourselves.
Opinions on MS and C don't apply. There are many other threads talking about this - although they seem to get locked after a while...
For some who seem to believe that i think C# will replace VB6 / .NET / C++ is wrong. I didn't say that. I said its pushing it more and more out of the water and more companies would rather have you do something in C# instead of VB or C++. Now, When i say i am being pushed towards other programming languages other than VB6 and .NET what i ment was theres really 2 types of programming
- Maintenance
and
- Development.
Now days doing maintenance requires you to have a good base knowledge of older languages because it would be cheaper for companies to pay a developer to maintain it, rather than write the whole application in a more advanced language.
Development is usually creating new applications. And while there is more development companies want their applications in a new more advanced languages. Such as C#.
P.S- Does anyone know if VB6 will work after vista? I've read alot of different stories and everyone seems to have a different opinion. Yours?
They haven't said. In the next 1-2 versions of Windows it'll move entirely to 64-bit but I'm not so sure about VB6 support. Hopefully no one is using it anymore at the point when they need to / want to upgrade to an even higher version of Windows.Quote:
Originally Posted by John_420
i dont think its going to be the next version. It comes out in 2009. However they seem to be moving to providing both versions on one dvd.Quote:
Originally Posted by kasracer
Click the "47" under REPLIES...Quote:
Originally Posted by John_420
Who is "we"?
My last two jobs wouldn't allow development in C# (and by extension, C/C++). Everything is done VB.Net. The reason isn't functionality or practicality - it's economical. Statistically, more people have an easier time grasping VB.Net rather than C#. This means the resource pool for developers is larger and for the most part; cheaper.Quote:
Originally Posted by John
While I realize "2 companies" is no where near the scientific control needed to prove my point; given my experiences and others I've talked to - it is sufficient enough to discredit your blanket statement.
At this point I could go on about "choosing the right tool for the job," but that has been summed up very well by the previous posts. So I'm not going to touch it.
As for the actual topic (and this has been said but deserves reiteration); MS has been very clear about their views on future development on their platform. .Net is the way they are going. If you're a young developer; I would urge that you ramp up. If not, I'm sure the Java camp would also love to have you.
#include BadAnalogy.h //Because I love them soo soo much
Picture .Net as a minivan. MS is our dad and us developers are a bunch of kids. Dad told us we're taking a family vacation to the Zoo. Dad's already got this planned. He's mapped out the route we're going to take, planned breaks and bought the zoo passes. All that is left is to load the kids into the van and take off. Some of the kids got in the van and are happy to see the animals... Others, not so much:
Some whined they want to go to Disneyland, but dad already has the passes.
Some of them just wanted to stay home and watch tv, but dad can't leave them home alone.
And a few others got on the van, but will cry the whole way there making the trip unpleasant for all.
Luckily for them, Child Protective Services (US courts) lives right next door and has seen this debacle taking place. Otherwise, dad would have taken his belt off long ago...
Regardless of whether you're actually doing your coding in VB.NET or C#, you should try to keep up to speed on the other, since by knowing one, you're 90% of the way to knowing the other, so you may as well play around with it a bit in case a job interview comes along that specifies one or the other.
Additionally, if you know either, you're 80% of the way to being able to pass yourself off as a Java developer, so you may as well learn the other 20% if your career goals include working for some hippy who'll pay you in peanuts (or however the hell the Java development community works).
:confused:Quote:
Originally Posted by John_420
What do you mean by that first sentence? Care to elaborate?;)
You often do not code the same type of applications in C++ and C#, so comparing them isnt really fair. Thats like comparing a race car with a bulldozer.
Edit: dang, i didnt realise this browser-tab was an old one...thought i was replying to the freshest post of them all :D
This post can be ignored. ;)