IAMA C++ Ask Me Anything

Go ahead, I, the mighty, wonderful, beautiful, athletic C++ will answer all your questions!

>>38
Well... Go barely achieves anything more than D, but people still welcome it like the second ejaculation of Christ. And you probably aren't old enough to remember it but Java was received the same way by all the seppelgoobers who didn't know how caches worked and had total faith in the perpetuity of Moore's law. I guess usability is just one of those hard problems with unfathomable search spaces and it's human nature to blunder cluelessly in and out of local maxima.

The most depressing thing is that while individuals learn from their mistakes some of the time, societies don't. Oh well.

>>41
Java is a completely bad example.
It was designed to be a clean C++ for scripting purposes, on the client-side web.

But it failed, thanks to Netscape mocha/livescript (later Javascript). Somehow it became useful for JSP/Servlets, and now the “Compile Once Run Anywhere” is just bullshit that people don't care anymore.

>>41
But Go doesn't claim "to be better than C++". In fact, Go was actually called "Lingo" once; They revived the old project, gave it a new name and runtime.

IAMA dubs AMA

Oh mighty C++ hear my prayer.

How do I put a torch under my ass and actually learn a programming language?

I learned BASIC in 1992.  HTML in 1996. I have learned nothing well enough since.

You must read the holy book, The C Programming Language, by Kerrigon & Ritchy, and do all the exercises in the book.

Learn D

ick sucking

>>45
How do I put a torch under my ass and actually learn a programming language?
Programming isn't about knowing a language. It's about setting goals and figuring out what problems to solve (and then solving them, of course). You already learned BASIC and you're not a programmer yet, so obviously "learning a programming language" is not the right problem to solve to get to your goal.

Picking which problems to solve when you're first learning to be a programmer is pretty fucking hard because it usually has to be something you actually care about, or you'll never solve it. So step one should be to ask yourself ``what do I want my program to do?'' This question is also very important for deciding which language to use. You wouldn't write an operating system in Ruby or Python, and you really don't need a monstrosity like C++ for a script that just renames a bunch of files on your desktop.