[mellosouls]

Thanks for sharing your experience.

One minor critique: the vim stuff looks like a red herring given the topic. I'm personally not particularly interested in vim but am interested in jupyter notebook-alternative setups - I'd either remove it or explain why it's relevant here or contextualise it in some other way.

[205g0]

Good point, I should have explained it. To get into vim takes time and to get muscle memories at least 9-12 months. Something a lot of coders even don't do, so why should a data scientist do this. The result is that you are so much faster because most of the time you don't write code but stare at your code, navigate around and do small changes. So, I think if you deal with code 80% of your day, vim binds are a must and this was my biggest gripe with these notebooks. Google Colab is the only notebook offering painless vim binds. No other notebooks has proper vim support because data scientist are not coders and rather care about math.

[mpalmer]

It's relevant to him and his experience not to mention that of plenty of other developers. Why tell OP to remove it when you can just ignore it?

[mellosouls]

Was clearly suggesting, not telling. And clarification was suggested also as an alternative.

In the context as described it's not obvious why it's relevant (especially to a non-vim user).

Constructive feedback was being offered, is all.

[amingilani]

I second this. I couldn't understand if it was important to the setup or just a nice-to-have feature. There's no context.