I took a quick glance at that and will read more deeply, thanks. I was mainly curious about why it was that caused it to be slow and I see that article vaguely mentions it though not in much detail.
Your second part is a point I keep seeing being made and I can't really agree with it. If I don't do something interesting I won't learn anything because I won't do anything. I've been trying to learn C++ for about 4 years now and still don't understand much. I've read over 10 books on C++ and watched three entire c++ tutorials on SFML and Allegro as well as other small videos. I fear I'm just a very slow learner with this type of thing but I have 0 artistic abilities in other areas while with programming I think with perseverance I can actually create something eventually which is a dream of mine. This isn't something that just clicks for me so the only way I learn is to actually do something I want to and figure it out as I go. I've learned a great deal about C++ simply from applying it and fiddling with it until it works with SFML. I'm a very hands on learner and just reading things makes almost no sense to me. So, basically, I'd argue that learning C++ from C++ books AND SFML at the same time is a very good idea as I can actually put into application what I learn in the books so it makes sense in a real sense for me.
I did try looking at the source, but to be honest it's still beyond me at this point to really understand. Was just hoping for a simple explanation to start on.
I hope you don't take me as ungrateful, however. That article you gave me really does look interesting though and I am thankful for your response and link.