Regarding C and C++ (64)

24 Name: #!/usr/bin/anonymous : 2008-05-09 11:35 ID:Heaven

Post split again.
>>22
What absolute twaddle.

What is your goal?

If it is to learn computer programming, you should understand that C and C++
were made to solve programming problems of decade sgone by. They are old and
showing their age. Better languages have been released.


That's absolute bullshit. C was originally written for low level work with unix.
If you believe that in 2008, unix isn't relevant anymore, you are absolutely
delusionary. C's problem is that it's too simple; it's missing things
every program would use. C++ was designed (and is) as a more complete alternative
to C. And your claim that both languages are old is outrageous! C++ isn't old!
(An example of an old language still used would be lisp, and not C or C++)


If your goal is to support legacy code, or modify the linux kernel you should
learn C and C++.

Yes you should, so you can take the legacy code and write a better portable
solution in C or C++.


If you want to make modern desktop apps, then you need to go with a different
langauge and/or programming platform. C++ (as a language) is ill suited for the
task. By default objects are passed by value, which isn't object oriented at
all. Threading (which is becomming so important these days) is a pain in the
ass.


Again, bullshit. Why is C++ ill-suited? Why would it want to be "object oriented
by default"? Objects can be passed by reference in C++ (not in C thought)

int zero(int &i) { return i = 0; }

Moreover, the new C++ standard is going to include threads, and you'd know that
if you were a C++ programmer, which apparently you are not and you're talking
out of your ass. C++ is a multi-paradigm language, and includes OOP in the list.
It's not forcing OOP down your throat.

Just when was threading not important? Please help me recall.
Also, explain briefly the issues you have encountered with libraries such as
pthreads. Do you even know when to use threads and when not?


If you want to make Windows/Web/some mobile/limited Linux apps, go with
C#/VB.Net and the .Net framework.

Why would you go with C# and .NET for linux apps? What about BSD, solaris,
other? OP: Don't learn C#.


Or go with Java. The platform absolutley sucks, but the language isn't half bad.


No, don't go with java. Stick to C as it's more portable, it's controlled by ISO
(and not Sun), it has very good implementations and it can do things Java
wouldn't imagine of (embedded programming, low level stuff).
Java sucks, but I can understand learning it. Sun is a good company. C#? C# is
horrible. It's controlled by microsoft. For fucks sake, OP, do not learn
C#. If you want, try java after learning C, do not concurrently learn them as it
might confuse you.
This thread has been closed. You cannot post in this thread any longer.