The main issue with C++ is the amount of undefined behavior and the very high amount of knowledge you need to write "legitimate" code.

There's just so many pitfals.

That being said - I really love it. It's my favorite language by far.

Is writing a voat comment "coding"? Because if not - then HTML isn't coding either.

The stupidest thing I could ever imagine someone would say about Unicode would still be better than this nonsense.

Javascript is a horrible, messy language. It shouldn't be an example for anything.

Yes, until now he mostly took toy examples and considered them as if they were in a vacuum - completely missing the point of the example.

But he has raised a few very good points that I - as someone who HAS worked on a large number of big, complex projects with similar / recurring elements - have encountered and agree with:

• In OO, who should be responsible for the interaction between two objects? "Functions" sound like a better option than "randomly choose one of them" or "create a new interaction object". Example: readline between an std::istream and an std::string in c++.

• Sometimes - more often than I would have liked - I suddenly need access to the functionality of an inner object of an inner object of an inner object of the object I can see. The solution is annoying: create a set of "proxy functionality" for all the objects in the hierarchy. That is bad because: (a) I now need to create a ton of new tests for basically nothing, (b) I now need to "change the story" of each of these objects to explain why having that functionality makes sense with their "design" and (c) it's just a ton of extra code for something very small.

• "Design", or "what does this thing I need really mean" is an interesting and fun exercise, but when you just want something that "works", it's an annoying distraction that costs you money. How many times did you have code that actually did what you wanted perfectly, but you had to rewrite it from scratch because you found a better "design"? It happened to me very often. Is it worth it? In OO it's essential. But if it was programmatic? I'm not sure you need it then.

Small things make sense as objects - like strings and such. But even with strings - strings! - the rigidity of objects is creating problems. Want to add a "write on change" functionality where sub-strings are very cheap? Oh, sorry, your original design called for iterators to be persistent when changing a character. So you now can't do that very important thing that would have helped a lot and make some code substantially faster. Even when some people don't use iterators. Because OO. Too bad.

xfce all the way. For development? Yea, xfce.

None. You don't need to read any books. The books are only good once you already know how to program.

To learn, "just do it" and use google to find short examples / demos. That and stackoverflow.

Can confirm. Been programming in C++ and python for over a decade, and php for around a year. Just started a new job where they work in Java.

No problem. "everything is a pointer, . is actually ->, there's no *, that's it".

Annotations still annoy me (in the sense that I don't have a good enough understanding of them to create my own), but other than that - I don't feel like I'm missing anything.

my experience, it's not necessarily an intelligence problem but rather a passion one.

Yes! Exactly!

I remember when C++11 just came - I was so excited! I send all my free time (at home!) playing around with the new language features. I was reading about it for years before - when it was still C++0x - almost getting a boner about the auto and new for feature, and trying to wrap my head around promises and futures. And I wasn't alone - for months, all we talked about at work was this new thing or that new thing in C++11, and how we would write things differently, and how SFINAE works, and what we could use it for, and how we would change the codebase to take advantage of the new features and... and... and we were legitimately excited. Like the hype you get before a new video game / movie / whatever comes out.

Female programmers? No. They just "OK, this is a new thing I need to learn. Hopefully I can just continue to work as normal". Not one looked like she would spend her free time excitedly reading anything she could find about the new features. They work, they go home, and at home they don't think or care about programming.

That's the difference I see.

That's weird, because I've been programming for decades now professionally for many different companies, and I've yet to meet ONE good female programmers.

Oh, there were some competent ones (as good as the worse male programmers at the company), and a lot of really bad ones (that would never have been hired if they weren't women), but not ONE good programmer. Not ONE programmer you could say had passion, wrote inspiring code, was excited to see some new form of data structure or programming idea.

In decades of professional programming, and decades of (private tutoring) teaching, seeing many many both male and female programmers (admittedly, mostly male), not a single good female programmer. But many many good male programmers and a lot of excellent programmers.

And I'm still using php5 (that's the default on ubuntu?)

That's the opposite of dataisbeautiful :(

What horrible graphs, and no graph comparing the different file systems! Really, I'd love to see a comparison, but this article did a piss poor job displaying the data.