Originally posted by: brandonb
The languages I see out there in the field being used regularly:
C#
VB.Net
Java
Learn those if you want a job.
I'd agree that the percentage of programmers that understand memory management will go down but I'd bet the absolute number is going slowly up if it's moving. I think that's a good thing too. As we develop nice environments that abstract away scary things like memory management it's only natural that more developers spend more time thinking about higher level things. Somewhat depressingly, I'd bet the iq of the average developer is going down as the field turns more into a trade than a science.Originally posted by: Markbnj
It won't be too long before nobody has a working grasp of how memory operates anymore. Maybe the O/S designers and compiler-writers, or driver programmers, but at some point it will probably be abstracted away into hardware and not even dealt with by them.
Originally posted by: brandonb
The languages I see out there in the field being used regularly:
C#
VB.Net
Java
Learn those if you want a job.
Originally posted by: brandonb
The languages I see out there in the field being used regularly:
C#
VB.Net
Java
Learn those if you want a job.
Originally posted by: jman19
Originally posted by: brandonb
The languages I see out there in the field being used regularly:
C#
VB.Net
Java
Learn those if you want a job.
He's going to school for computer science. He shouldn't be worrying about what language will land him a job now, he should be worrying about knowing the important concepts in CS...
Originally posted by: Tencntraze
Originally posted by: jman19
Originally posted by: brandonb
The languages I see out there in the field being used regularly:
C#
VB.Net
Java
Learn those if you want a job.
He's going to school for computer science. He shouldn't be worrying about what language will land him a job now, he should be worrying about knowing the important concepts in CS...
I agreed with this statement about what will get you a job, but that's also why I wish they still taught C++ first so that you are exposed to all of the underlying concepts (the science portion of the degree).
Originally posted by: Tencntraze
I went to Northwestern and they also started us on Scheme for the same reason. I later did some LISP for some AI class, but Scheme did help me with initial concepts of iteration vs recursion and all that good stuff.
Originally posted by: Tencntraze
I went to Northwestern and they also started us on Scheme for the same reason. I later did some LISP for some AI class, but Scheme did help me with initial concepts of iteration vs recursion and all that good stuff.
Originally posted by: cwdegood
Thanks for all of the replies.
I really do appreciate the help you have all offered.
I just wasnt sure if C# had matured to a level of market acceptance.
Thanks again for helping me steer my life
Memory management is very important, but it isn't an easy concept to master and should be introduced after other concepts.
Originally posted by: bsobel
Memory management is very important, but it isn't an easy concept to master and should be introduced after other concepts.
So what are we going to teach once garbage collection is formally added to the c++ standard (It's in work, one of my co-workers is one of the primary guys behind it).
Originally posted by: Dhaval00
Originally posted by: bsobel
Memory management is very important, but it isn't an easy concept to master and should be introduced after other concepts.
So what are we going to teach once garbage collection is formally added to the c++ standard (It's in work, one of my co-workers is one of the primary guys behind it).
The C++/CLI built on top of the CLR 2.0 already does this...
Memory management is handled by the CLR, but it is still very important. I personally, manually dispose (using blocks) all my objects in my C# code to minimize garbage collections at the CLR level... I know quite a few developers who went to private universities and don't dispose their objects - they take memory management for granted. Simply put, they either were trained primarily in C# without formal knowledge of the internals of the CLR or had no classes in native C/C++.
Originally posted by: bsobel
Your approach is just as wrong as their's. Dispose is only usefull if you have unmanaged items to take care of. Your not minimizing garbage collection and your fighting the system when you shouldn't be.
Originally posted by: bsobel
Originally posted by: Dhaval00
Originally posted by: bsobel
Memory management is very important, but it isn't an easy concept to master and should be introduced after other concepts.
So what are we going to teach once garbage collection is formally added to the c++ standard (It's in work, one of my co-workers is one of the primary guys behind it).
The C++/CLI built on top of the CLR 2.0 already does this...
Of course it does but thats not real c++, I'm talking about the ansi standard here not MS's extensions.
Memory management is handled by the CLR, but it is still very important. I personally, manually dispose (using blocks) all my objects in my C# code to minimize garbage collections at the CLR level... I know quite a few developers who went to private universities and don't dispose their objects - they take memory management for granted. Simply put, they either were trained primarily in C# without formal knowledge of the internals of the CLR or had no classes in native C/C++.
Your approach is just as wrong as their's. Dispose is only usefull if you have unmanaged items to take care of. Your not minimizing garbage collection and your fighting the system when you shouldn't be.