Re: C # and C ++ learning curve
- From: "Deckarep" <deckarep@xxxxxxxxx>
- Date: 20 Jan 2007 20:20:25 -0800
One thing I like about C# is the fact that if and when you need to jump
into other languages they are many that look/feel like c#.
For example Java, ActionScript( Flash ), JavaScript, PHP and others.
They all borrow from the family of C languages but more languages like
C# are offering memory managed environments therefore making C# (in my
opinion) the better choice.
I have the utmost respect for any true C++ programmer and I can only
wish that I understood the hardware and memory aspect of things like
they do but the fact is, it's becoming more specialized.
Companies are looking for rapid development over speed and control. I
mean, imagine programming a Web Application in c++. Of course it can
be done but the C# team will pump it out faster. True, they may not
understand data structures, hardware, and memory management as much as
a c++ programmer would but in many settings rapid development is
favored over those things then if need be performance is squeezed out
by moving to the lower level (read: c++).
I'm sure I might get people who would argue this fact but all you need
to do is look at the market. Like I said I give it up to c++ coders
but I'll stick with my managed world until the need arises and the
ground opens up and eats me alive. Which I know will happen someday.
Haha,
-Ralph
Sidenote: The only reason I say that some people may not understand
data structures, hardware and memory management is for some obvious
reasons and some not so obvious. I love the fact that the .net
framework has all these built in classes ready to go. But the downside
is unless I truley delve into these classes and figure out in detail
how they work I may not understand them as effectively as someone who
has to build these structures from scratch. True story: a programmer
interviewed for this company. He was asked when he would use some data
structures over others. His argument was that it was all user
preference. Meaning they all did the same thing...but you just had to
choose what you preferred. Nevermind having to worry about sorting,
lookup speed, hash collisions, etc. Forget about O notation...he just
figured it was all preference and that all data structures performed
the same. Unfortunately this is common in the managed, framework world
of developers. I'm guilty of it sometimes too. People can have a
tendancy to not really understand why different classes exist in the
first place.
Peter@POLKO wrote:
Hi Complete ass here trying to get his feet wet in .NET programming. I want
to start easy, understanding what is talked about. Which of these two would
be a better choice, if same, which one is consider easier to learn first?
Thanks for any advice
.
- Follow-Ups:
- Re: C # and C ++ learning curve
- From: MrAsm
- Re: C # and C ++ learning curve
- References:
- C # and C ++ learning curve
- From: Peter@POLKO
- C # and C ++ learning curve
- Prev by Date: Re: What's the difference between these two ways of adding delegates to a Generic List object?
- Next by Date: Re: A quick Newbie to NET question
- Previous by thread: Re: C # and C ++ learning curve
- Next by thread: Re: C # and C ++ learning curve
- Index(es):
Relevant Pages
|
Loading