I fully agree with the crappy documentation. Which to be honest isn't consistent with the rest of the python sphere. Documentation tends to be pretty good generally. It's a shame.

Hmmm, I did a bit of searching and didn't find anything I particularly liked, I guess I'll add this to the list of posts I need to write. Nevertheless, I did find something. Check out these links:

http://matplotlib.org/users/artists.html

http://matplotlib.org/users/transforms_tutorial.html

http://matplotlib.org/users/path_tutorial.html

http://matplotlib.org/users/event_handling.html

Whether they are a reinvention or not, can't I be ebullient about them? I love new technology for example, and I get pretty ebullient about whatever new things there are. It doesn't mean that I'm ignorant of the past that has led up to them and it certainly shouldn't effect my thoughts on them either.

Yeah it's 1.5 times larger. It was a joke though because Japanese people always say it never stops raining in the UK, it's like the first thing they always say.

That's what everyone seems to say about the UK.

That's true haha. It rains a fair amount but it's definitely over exaggerated.

That's a good point, I've ran into problems with that before too. Thanks.

That is true, the maths is very basic and it doesn't go into why it's blazingly fast. The reason for this is that it doesn't fit the idea of this series at all.

However that would be an interesting post, it will be a good one to write, but not part of this series.

Thanks!

Yeah, I'm not too impressed by the Google API documentation if I'm honest. Using the API via HTTP is quite well documented, but using the api via their python library... Not so much.

What's the problem?

It's different than any other side and somehow slower and a little bit delayed.

Well it has a smooth scrolling effect on it. Does it lag? Is it inconvenient?

Any feedback on anything to do with the blog is welcomed and appreciated.

Yes it's a little bit inconvenient. I have smooth scrolling enabled in my browser and it seems those two don't work together ;)

Ah I see, thanks for telling me!

If you're going to be accessing user data, you need to be using oath authorisation. There are other ways to handle it but after a lot of research and trial and error, in the end this was the best way I found.

Honestly, I have no projects or specific uses for these languages. Rather, I am treating it as a tool for learning and to experience low level programming.

I might make some kind of machine learning application in it later down the line though.

The usual recommendation "for learning and to experience low level programming" would be C. See this for example http://www.joelonsoftware.com/articles/CollegeAdvice.html although that was written before Go and Rust.

Also if you're mucking about with machine learning a lot of the libraries seem to be in C or C++. I played about a bit with computer vision using Python but sometimes the Python bindings don't work or don't exist and I was thinking it would be easier to just call the things from the C/C++ they are written in.

We're actually growing a rather nice machine learning ecosystem on the Rust side, though obviously it's much less mature than the C/C++ solutions. See https://github.com/autumnai/leaf/blob/063ce978004b8bf4b7fc74... for an example.

In that case, I would recommend Rust because it's just harder to learn than the other options.