Guido van Rossum

Between, I'd say, 2013 and 2018...

I dabbled with PyCharm, mostly because it had a couple of features.

I mean, PyCharm is like driving an 18-wheeler truck, whereas Emacs is more like driving your comfortable Toyota car.

that you've had for 100,000 miles and you know what every little rattle of the car means.

I was very comfortable in Emacs, but there were certain things it couldn't do.

It wasn't very good at that sort of, at least the way I had configured it.

I didn't have very good tooling in Emacs for finding a definition of a function.

When I was at Dropbox exploring a 5 million line Python code base, just grabbing all that code for where is there a class foobar?

Well, it turns out that if you grab all 5 million lines of code, there are many classes with the same name.

And so PyCharm sort of once you fired it up and once it's indexed, your repository was very helpful.

But as soon as I had to edit code, I would jump back to Emacs and do all my editing there because I could type much faster and switch between files when I knew which file I wanted much quicker.

And I never really got used to the whole PyCharm user interface.

Yeah, you have to just want to learn that.

I mean, if you don't need it much...

If you do a lot of keyboard input.

Here we go again with the spreadsheet of my life.

I'm not going to stop you.

I think that sort of everybody has to decide for themselves which one they want to invest more time in.

I actually ended up giving VS Code a very tentative try when I started out at Microsoft and really liking it.

And it took me a while before I realized why that was.